[Log] Issues Installing Ubuntu 14.04

0. Don't use UEFI for usb boot.

Won't recognize windows system.

1. Network. DHCP not working.

remove

auto eth0
iface eth0 inet dhcp

1.5 SSH auto start

sudo update-rc.d ssh defaults

2.  VNC Server

sudo apt-get update

This updates the package list for apt.

---

Then you'll need to install the Gnome components using Software Center:

Or Using Terminal:

sudo apt-get install gnome-core

---

To install VNC server using Software Center:

Or Using Terminal:

sudo apt-get install vnc4server

VNC view gray screen

edit ~/.vnc/xstartup

#!/bin/sh

def

export XKL_XMODMAP_DISABLE=1

unset SESSION_MANAGER

unset DBUS_SESSION_BUS_ADDRESS

gnome-panel &

gnome-settings-daemon &

metacity &

nautilus &

gnome-terminal &

3. Start VNC

vnc4server -geometry 1280x1024 -geometry 1024x768 -geometry 800x600

switch resolution

xrandr -s 0

4. Mount Windows Partitions.

fdisk -l

sudo mount -t ntfs -o nls=utf8,umask=0222 /dev/hdb1 /media/c

5. Internet Down for strange reason again.

Seems like it is a network manager bug

5.1. Purge network manager

Gnome:

sudo apt-get remove --purge network-manager-gnome network-manager

KDE:

sudo apt-get remove --purge knetworkmanager network-manager

reboot required. ifdown ifup won't initi the network.

5.2 Setup DHCP.  and name server
/etc/network/interfaces

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

5.3 Setup DNS nameserver
/etc/resolv.conf
nameserver 128.223.6.7
nameserver 8.8.8.8
nameserver 8.8.8.4

OR static

auto eth0
iface eth0 inet static
address 10.0.0.100
netmask 255.255.255.0
gateway 10.0.0.1

6. Command Not Working in 14.04

/etc/init.d/networking restart
sudo ifconfig eth0 down(up)

Use

sudo ifdown (ifup) eth0


7. Skip Login Screen.

source.
http://askubuntu.com/questions/148717/how-do-i-boot-into-the-console-and-then-launch-the-ubuntu-desktop-from-it

down voteaccepted

To return to the login screen Press Ctrl+Alt+F7 to return to the login screen. You can exit your terminal session on tty1 by typing exit before you do that. Doing startx -- :1 will start another X session under terminal tty1, logging you in directly (use :2, etc. for even more displays). Note that logging into multiple sessions as the same user is not recommended and could lead to system instability. To skip the login screen completely, boot into the console and then start the GUI, you must modify GRUB: sudo nano /etc/default/grub Change line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="text" Ctrl-X, press Y and then Enter to save and exit. sudo update-grub Reboot and you should come up directly in tty1 -- no need to press Ctrl-Alt-F1. Login, and then startx to boot into the default desktop, or unity for Unity unity-2d-shell for Unity 2D gnome-shell for Gnome sudo service lightdm start to get the login screen (if you fix it :)

7. Ethernet problem

Might because of the intel network driver.
Last working setup
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp

Reboot doesn't work?
Must be shutdown at start?

OK. The answer is the intel ethernet driver. (It is strange sometimes it can work even without driver...)

From the logs it seems to me you have managed to update the driver from version 2.3.2-k to 3.2.4.2-NAPI.

I fixed my Intel NUC non working ethernet by:

• download the driver from https://downloadcenter.intel.com/download/15817, currently 3.2.4.2 (as shown in lshw -C above)
• make install in the src folder
• rmmod e1000e
• modprobe e1000e
• and to make the new driver survive a reboot update-initramfs -u

This I have to repeat at every kernel update, since kernel updates still (3.13.0-63) contain the old driver version 2.3.2-k, which does not work with my Intel NUC.

http://www.intel.com/content/www/us/en/support/network-and-i-o/ethernet-products/000005480.html?wapkw=(itanium)

8. How to prevent “Write Failed: broken pipe” on SSH connection?

needed to have rw for user only permissions on config. This fixed it.

chmod 600 ~/.ssh/config