Edubuntu internet connection problem ??

[Abarbarian]

Ha ha !!! Me Edubuntu would not connect to the internet so I fiddled about and deleted some info. Then I found out I had forgotten to plug in the cable.

So in me Network settings window once you click on the connection properties you get several tabs. Under the DNS tab there is no info for which DNS server to use and it asks to input the address.
What do I type in there ??
I have the Wired Connection set to DHCP Auto so that should sort itself out automatically.

Its not as easy to negotiate as Mandy, at least not from the GUI and I don't know enough about the command line yet so do not want to mess around with it. Me pc is nicely set up and updated so I don't want to start all over again.

 

[Waynos_Face]

its normally a bunch of numbers like your IP,

255.255.255.0

 

[Urmas]

Under the DNS tab there is no info for which DNS server to use and it asks to input the address.
What do I type in there ??

No need to type anything in there... just reboot. It'll get the DNS info from ISP... or your router, if you have one.

 

[Abarbarian]

Have a modem/router. Used to work fine, take out the cable and stick it in either pc and I got connection. Now it don't work. Darn.

 

[Urmas]

Do Skype & email work? If yes, it's not a DNS issue.

But...

sudo ifup eth0

(assuming eth0 is your active ethernet device) is worth a try.

Also:

ifconfig

Here's mine (eth1 is my active device):

urmas@rocinante:~$ ifconfig
 eth0	  Link encap:Ethernet  HWaddr 00:e0:7d:b1:89:a2  
 		  UP BROADCAST MULTICAST  MTU:1500  Metric:1
 		  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 		  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 		  collisions:0 txqueuelen:1000 
 		  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
 		  Interrupt:16 Base address:0xd000 
 
 eth1	  Link encap:Ethernet  HWaddr 00:0c:76:30:a2:69  
 		  inet addr:192.168.1.100  Bcast:255.255.255.255  Mask:255.255.255.0
 		  inet6 addr: fe80::20c:76ff:fe30:a269/64 Scope:Link
 		  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 		  RX packets:5788946 errors:0 dropped:0 overruns:0 frame:0
 		  TX packets:3613926 errors:0 dropped:0 overruns:0 carrier:0
 		  collisions:0 txqueuelen:1000 
 		  RX bytes:3386789273 (3.1 GB)  TX bytes:424171012 (404.5 MB)
 		  Interrupt:19 
 
 lo		Link encap:Local Loopback  
 		  inet addr:127.0.0.1  Mask:255.0.0.0
 		  inet6 addr: ::1/128 Scope:Host
 		  UP LOOPBACK RUNNING  MTU:16436  Metric:1
 		  RX packets:3966840 errors:0 dropped:0 overruns:0 frame:0
 		  TX packets:3966840 errors:0 dropped:0 overruns:0 carrier:0
 		  collisions:0 txqueuelen:0 
 		  RX bytes:1658549270 (1.5 GB)  TX bytes:1658549270 (1.5 GB)
 
 urmas@rocinante:~$

 

[Anon_F]

Then I found out I had forgotten to plug in the cable.

Glad to know others have done the same as me in the past!!

 

[Abarbarian]

Have me UTorrent on a usb 8 GB hdd and could not understand why it kept on screwing up. Spent three days checking this and that and fiddling about. Was a real pain.

Then I realised that every time I switched me monitor of to save electric I had problems with the UTorrent.

Silly old me had pluged the drive into the monitor usb socket instead of the usb extension cable I normaly use from the pc.

I'll give that a try Urmas. Will post back.

 

[Urmas]

Oh, and:

... so I fiddled about and deleted some info.

Flipism applied to computing... every forum needs a designated crash test dummy.

(Couldn't resist... should've, just couldn't... sorry, mate!)

 

[Abarbarian]

Thats ok .

Gimme a medal

 

[Abarbarian]

sudo ifup eth0

Did the trick Urmas.

 

[Urmas]

Gimme a medal

Naah... here's a badge, though:

 

[Abarbarian]

Ta fer the key to the city badge.

Can you help me with the above ?????

 

[Urmas]

Holy crap, Batman! How did you... nevermind. Do:

sudo rm /var/cache/apt/pkgcache.bin /var/cache/apt/pkgsrccache.bin

 

[Abarbarian]

Gimee another medal he he.

I had the update manager set to download and install updates automatically. So that was why I could not get access .

All 145 updates installed , Thats 70 days since I last updated. Took 34 minutes on this old P4 1.5 Ghz with 1GB of ram. Thats not bad at all. Is a little slower than me other pc for surfing but not too much and is certainly a useable pc. Mind you downgrading to a 17" monitor and a mouse with no scroll wheel is definitly not good.




Saved your tip for future use though just to be safe.

 

[Urmas]

Gimee another medal he he.

I can do better than that... the ultimate terminal entertainment; enjoy:

telnet towel.blinkenlights.nl

 

[Madxgraphics]

I can do better than that... the ultimate terminal entertainment; enjoy:

telnet towel.blinkenlights.nl

That was cool, Haven't seen it in a while though

 

[Abarbarian]

 

[Abarbarian]

Well everything was going ok with the updates. All I needed to do was restart. So I did.

Strat up screen was as normal. Then it kicked up a screen saying that the Pre Release X Server stuff was not working properly. Did I want to see the log file. So I said yes even though I do not know what it all means. Followed several other screens and finaly ended up with a window saying.

The xserver is now disabled. Restart GDM when it is configured properly.

So I hunted the net and could only find this advice to run,

sudo dpkg-reconfigure xserver-xorg

I hit Ctrl/Alt/F1 to get a command line and ran it.

Followed the screens and instructions and ended up back at the command line. Nowt had changed.

So what do I do now ??

I'm a bit narked that an ordinary uppdate has done this to me.

 

[Urmas]

Ati? Nvidia? Which drivers? If you install from manufacturer's pages (and not from repos), this'll happen after a kernel upgrade.

Other than that... GREMLINS?



Tools for idle hands:

#1. Boot using the previous kernel... Immediately after the BIOS screen comes up, you will just for a second, see where it says in the upper left to ‘press Esc’ for more options. This is your hidden GRUB (boot) menu, press Esc and then select the third line down. This will allow you to boot into the kernel you were using previously. Got GUI? Still no joy?

#2. Reboot "back" to latest kernel. Assuming you're using a proprietary Nvidia driver ("nvidia"), change it back to generic "nv":

sudo nano /etc/X11/xorg.conf

Nano is... Nano; first, "arrow down" to the following section...

Section "Device"
  	Identifier	"Configured Video Device"
  	Driver		"nvidia"
  	Option		"NoLogo"	"True"
  EndSection

... change "nvidia" to "nv"...

Section "Device"
      Identifier    "Configured Video Device"
      Driver        "nv"
      Option        "NoLogo"    "True"
  EndSection

... hit ctrl-x and then hit y to save.

Fingers crossed now:
abarbiturate@problemputer:~$ startx

 

[Urmas]

UPDATE -- fuggedabout the above post for a moment:

I've searched the Ubuntu Forums for this one; nothing epidemic. But looky here (from post #17 onwards):

http://forums.scotsnewsletter.com/index.php?showtopic=21743&hl=

"nvidia" --> "nv" DID help there. However... looks like there is an updated nvidia driver (and who knows what else) in repos today. So... before going through the hassle as per my above post, just do...

sudo apt-get update
sudo apt-get upgrade

... reboot. Might work. If not, do the "nvidia" --> "nv" edit in xorg.conf.