Member Avatar for Ahmed_I

Guys anybody faced this problem in Ubuntu 8.10 where when the cable is plugged in the PC it doesn't read any connection automatically like its predecessors.

If anybody faced this problem plz can he provide me with the solution ?

Note:-I've tried sort of things and noticed that in the terminal the connection is established and the packets are sent normally.

  • 2 Contributors
  • 3 Replies
  • 207 Views
  • 10 Hours Discussion Span
  • Latest Post Latest Post by Ahmed_I

Dani AI

Generated

Quick diagnostic note: on Intrepid (Ubuntu 8.10) the NetworkManager applet will often not auto-activate or show a wired connection if the interface is being managed by ifupdown (that is, it is declared in /etc/network/interfaces) or if NetworkManager is configured not to manage ifupdown interfaces. Changing which subsystem manages the device is the usual fix. (wiki.debian.org)

Practical checklist (do these in order; back up files first):

# Inspect what /etc/network/interfaces contains
cat /etc/network/interfaces

# If you see eth0/other entries, back up and edit to leave only loopback:
sudo cp /etc/network/interfaces /etc/network/interfaces.bak
sudo nano /etc/network/interfaces
# file should contain at minimum:
auto lo
iface lo inet loopback

Then make NetworkManager manage ifupdown devices (file name differs by version; Intrepid used nm-system-settings.conf, later versions use NetworkManager.conf):

sudo cp /etc/NetworkManager/nm-system-settings.conf /etc/NetworkManager/nm-system-settings.conf.bak
sudo nano /etc/NetworkManager/nm-system-settings.conf
# ensure:
[ifupdown]
managed=true

Finally restart NetworkManager so the applet and automatic activation update: sudo service network-manager restart (or /etc/init.d/network-manager restart). (networkmanager.dev)

If that doesn't restore auto-connect, check the device and logs and try DHCP from the shell to confirm behavior:

ip addr show
sudo tail -n200 /var/log/syslog | grep -i NetworkManager
sudo dhclient -v eth0

Also note the configuration file name may fall back to nm-system-settings.conf on older releases; see NetworkManager documentation for details. Back up before editing and use the static /etc/network/interfaces approach instead if you prefer manual control (both methods are valid). (manpages.ubuntu.com)

(As suggested, keeping the system updated is good — but for this specific symptom the steps above are the targeted fix.)

Recommended Answers

All 3 Replies

Member Avatar for jaimil27

Hello Ahmed_I,

Can you please provide me with extra information about your issue? Do you have router connected to the modem and properly configured?

The only solution I could provide for now is to turn off the modem and boot it up after 10 seconds!

Member Avatar for jaimil27

Since Ubuntu 8.10 was recently released, it is recommended to check for updates which would fix all the major issues with the system, whether it's Hardware, Video, Sound etc...

Member Avatar for Ahmed_I

Well jaimil27

Thanks for your contribution but i don't think the solution you suggested will solve my issue.

Because if its the modem's problem then why the internet connection works in windows ?
and the wireless in ubuntu is accessed easily without any configuration .

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.