Windows & Ubuntu

Screenshot.

 

[edit]

You chopped the title bar off in your screeny and it threw me.
***************************************************

Thats very strange.

 

Happy New Year - first post of the year and it's a tech support one! Probably not a good idea with a splitting headache too...

Intriguing that you are not prompted for your password despite the error. Can you try entering:

ping -c4 KVOWLES-UBUNTU and hit Enter and see if you get four replies, and then...

ping -c4 kvowles-ubuntu and hit Enter and see if you get four replies. It really shouldn't make any difference, but I want to see if the fact that your PC name is all caps is causing the issue.

Also, can you type in ifconfig and post up the output?

 

Check that the hostname has an entry in /etc/hosts, e.g.

Code:

127.0.1.1  KVOWLES-UBUNTU

Add it if it doesn't exist. Note: it IS case sensitive.

If you can't use sudo to edit the file, you may need to boot into "single user mode" to get root privileges(there should be a "recovery mode" option in the grub menu.

Edit /etc/hosts with a text editor of choice(vi/nano etc...) or add it to the file like this(note TWO ">" symbols, using only one will nuke the file):

Code:

echo 127.0.1.1 KVOWLES-UBUNTU >> /etc/hosts

In terms of your account not being an admin account, this is normal. The equivalent of "having an admin account" is having the permission to use the sudo command to elevate your privileges. Running everything as "admin" all the time is a very bad idea, and unnecessary, as all activities you perform as a normal user don't NEED the privileges that the root account provides, as all settings, documents and temporary files are stored either in your home directory, or in /tmp(world writable).

 

Might be nothing, but because I haven't added my user to the wheel group on my Debian system, sudo can be a bit broken. So I just type su, [password], command.

Maybe give that a go?

 

Screenshot.

 

This is highly irregular - you can't even ping!

Can you type in cat /etc/hosts and post up the output as well?

Give us some information about your general setup. Have you done any customisation to your network config in general or is your installation completely vanilla? What about your LAN - do you run your own DNS? Or are you using a garden-variety router?

 

I have done absolutely nothing in Ubuntu, fresh install. Except for installing the NVidia program.

Netgear DI524 router here, running a network of 4-5+ computers.

I'll post a screenshot in a few mins, gotta reboot into Ubuntu.

EDIT: Screenshot.

 

Ah OK, there's part of the problem - your hosts entry.

I did a quick test in a VM and got the following:


Click to view full size!

In your case, the issue is that you do not have a stand-alone entry for the name "KVOWLES-UBUNTU" - instead you have "KVOWLES-UBUNTU.AEIOU".

If you ping KVOWLES-UBUNTU.AEIOU you should find it works this time.

What you need to do is edit your /etc/hosts file and change the following:

127.0.1.1 KVOWLES-UBUNTU.AEIOU

...to...

127.0.1.1 KVOWLES-UBUNTU.AEIOU KVOWLES-UBUNTU

...so it can resolve to both names.

In my test VM, the following line is what was automatically setup, which matches my LAN configuration:

127.0.1.1 KVOWLES-UBUNTU.serenux.com KVOWLES-UBUNTU

 

Just thinking back now, I remember adding my network name somewhere in the network settings, however, I do remember also removing it afterwards.

Btw, AEIOU is the network name.

I'll check the settings, try the new terminal code & see what happens.

I'm seriously getting the shitties not only because I have to reboot into ubuntu, but also then use my TV as the default display, cause thats what ubuntu wants to use. Fucking stupid.

EDIT: By adding the AEIOU to the end of the computer name it appears to work. I get pretty much the exact same thing in your screenschot. I'll see if the network name was infact inserted into some of the network settings & try the ping without the network name.

EDIT 2: I just went through the network settings & it appears that I did remove the network name from the 'domain' field. However, in the 'Hosts' tab of the network settings window, I do see an alias of:
127.0.0.1 - localhost
127.0.1.1 - KVOWLES-UBUNTU.AEIOU

 

Hehehe - no worries - once you've got NVidia-Settings sorted, you'll be fine.

 

So.... after all that, how do I run the nvidia-settings?

Btw, I cant edit the ect/hosts file.

 

lol - you need to use sudo to edit that hosts file - problem is that you can't use sudo atm because of your hosts file issue.

Short of re-installing, reboot and choose "Recovery mode" from the GRUB menu. The system will do a partial boot and will ask you if you want to drop into a root terminal.

Once in that terminal, type in nano /etc/hosts (you won't need sudo because you're already working as root) and you will come into a terminal-based text editor. Make the necessary changes as previously described and then press CTRL + X, then "Y", then Enter.

Now reboot by typing in reboot and hit Enter. Allow the system to start as normal.

Once back into the GUI, drop into a terminal and type in sudo nvidia-settings and this time it should work!

 

Hallelujah!

Everything works as far as changing the display.

Now I can attempt at changing the default OS in the GRUB menu.

Does this actually change the order of OS's displayed in the GRUB menu? Like, does it change the boot order (normally it boots Ubuntu after 10 seconds) from Ubuntu to Windows?

 

Yay!

Changing the default x value simply changes where the menu highlight sits, and thus which entry will be started when the countdown timer hits zero. If it sits on the Windows entry, it will boot Windows first. If it sits on the first entry (as it does by default), then it boots Ubuntu. Menu entry order is not changed unless you change it yourself physically in the menu.lst file.

 

The line of code your talking about is this?..

Code:

# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default		0

 

Yep, that be the one.

 

What's a 'dmraid', btw?

EDIT: I made the change from 0 to 3, however, it includes the 'Other operating systems' as a selection. So, it's actually 4, in this case.

 

It's for discovering and activating software RAID sets.

 

Oh ok.

Well, everything is now running ok.

Thanks.