Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 605
  • Last Modified:

ubuntu 8.04 new motherboard, cannot get nic to work

I replaced an existing installation with a new motherboard.
Everything works, less the Network card.

I have removed the listings in
/etc/network/interfaces
/etc/udev/rules.d/70-persistent-net.rules
and rebooted

The new MAC address show up in 70-persisent-net.rules
I can set the Wired Connection to DHCP or STATIC, but neither provide access

When I go to Devices-Network Tools
under devices, I click on eth0 and then Configure, I receive an error, "The interface doesn't exist"
0
bmsjeff
Asked:
bmsjeff
  • 5
  • 4
  • 4
  • +1
1 Solution
 
rindiCommented:
You probably have a motherboard which is too new for your old OS. Try getting an Addon NIC, maybe one with a realtek rtl 8139 controller, that was a pretty common chip that worked with ubuntu 8.04 without problems...

Or update your OS to a current version....
0
 
nociSoftware EngineerCommented:
Other nics to consider are Tulip [ de2104x, de4x5 ] and generic version of this chipset.
They are also very common, various 3com adapters can also be considered.

Another approach can be if the hardware is much faster, to run the original system in as a virtual machine withing a new setup. [ in case you cannot upgrade the software, and timing is not too big an issue ].

Also consider that for the older adapters you do need a PCI slot available in your system.
0
 
Duncan RoeSoftware DeveloperCommented:
In a command window, run lspci which will show what is the model of NIC you have. Post the output - one can tell from that what is the oldest Linux revision (if any) that looks like it should support your card
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
bmsjeffAuthor Commented:
I will run the lspci command later today, after I resolve another issue.  Right now it is getting stuck on Samba at boot.  I have rebooted this machine at least 30 times since the new MB.
0
 
Duncan RoeSoftware DeveloperCommented:
Will Samba start without a NIC? I would disable Samba until you get a working network
0
 
bmsjeffAuthor Commented:
How do I go about doing that?  I am a newbie with Ubuntu.  Must I use a boot CD or is there a key combination for this?
0
 
Duncan RoeSoftware DeveloperCommented:
Sorry I'm not very familiar with Ubuntu. The general method would be to boot from CD, mount the normal root partition and modify the start up scripts therein. In system V start (which I think they use) you need to remove the symbolic links in /etc/rcn.d  (n goes from 0 to 5). Look for names of the form Snn*samba* (nn between 01 & 99)
Or it may be /etc/rc.d/rcn.d - you'll just have to hunt around a bit
0
 
nociSoftware EngineerCommented:
Ubuntu is debian based so:  http://www.debian-administration.org/articles/28

in this case:   update-rc.d -f samba remove
0
 
Duncan RoeSoftware DeveloperCommented:
@noci: thanks for that, but will it work from the rescue CD, or can it be made to? (chroot(?))
0
 
nociSoftware EngineerCommented:
If you chroot to the original root, then that will work. If you just mount it then rm of symbolic links will work too. becarefull to use the mountpoint as a prefix to /etc/rc*.d/...

Did you try to start with bash as init   (init=/bin/bash)  [ this cannot work if initramfs is used ]
or did you try to start in single user mode [ level 0] .

You can edit the command line [ i assume grub is used ] by moving the cursor to the right line after grub presents its menu and then press e
then add the word Single at the end of the kernel line.

After that you can use b to boot the kerne in single user mode. [ then no services will be started, except for the bare necesities ]
0
 
bmsjeffAuthor Commented:
lspci gives me:
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
0
 
nociSoftware EngineerCommented:
Afaict this chipset was new and from around the same timeframe as Ubuntu 8.
appearantly the linux kernel in ubuntu 8 could not select the right driver and chooses the r8169 driver in stead of the r8168 driver.

Here is a solution to help you get the right driver:
Before you try you can see if the driver is on your system by:

modprobe -r r8169
modprobe r8168
dmesg | tail -n 40

The first should remove an existing wrong driver, the 2nd should load the right one.
dmesg should show the kernel messages.

if no errors were reported then
ifconfig -a

should show an ethernet a interface...

The next article explains how to set it up for work after reboot.
  http://forums.linuxmint.com/viewtopic.php?f=49&t=80757

If you get errors like some stuff not found you de need a linux upgrade. Maybe Ubuntu 8 LTS might be a solution in this case.
0
 
bmsjeffAuthor Commented:
New info:
I followed "noci's" instructions.

I then changed the original /etc/network/interfaces from:

iface eth0 inet static
address 10.6.112.30
netmask 255.255.255.0
gateway 10.6.112.10

auto eth0

and changed it to:

iface eth0 inet dhcp


auto eth0


I then:
sudo /etc/init.d/networking restart

and get:
 * Reconfiguring network interfaces...                                          
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/d4:3d:7e:27:13:c0
Sending on   LPF/eth0/d4:3d:7e:27:13:c0
Sending on   Socket/fallback
DHCPRELEASE on eth0 to 192.168.0.2 port 67
There is already a pid file /var/run/dhclient.eth0.pid with pid 134519072
Internet Systems Consortium DHCP Client V3.0.6
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

Listening on LPF/eth0/d4:3d:7e:27:13:c0
Sending on   LPF/eth0/d4:3d:7e:27:13:c0
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 11
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
No DHCPOFFERS received.
No working leases in persistent database - sleeping.


Here is the ifconfig info:
mxc@mxc-nugent:/etc/network$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr d4:3d:7e:27:13:c0  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:17625 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:1192507 (1.1 MB)  TX bytes:0 (0.0 B)
          Interrupt:221 Base address:0x2000

eth0:avahi Link encap:Ethernet  HWaddr d4:3d:7e:27:13:c0  
          inet addr:169.254.5.187  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          Interrupt:221 Base address:0x2000

lo        Link encap:Local Loopback  
          LOOPBACK  MTU:16436  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:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)


If I go to Administration, Network Tools there are now two listings:
Ethernet interface (eth0)
IP Address: not available
Received packets - "it is receiving packets"
hardware address: not available
state: not available

Ethernet interface (eth0:avahi)
IP Address: 169.254.5.187
Received packets - "it is NOT receiving packets"
hardware address: d4:3d:7e:27:13:c0
state: active
0
 
nociSoftware EngineerCommented:
eth0 is the hardware interface
eth0:avahi is an alias interface based on eth0, so the packet counters are in eth0.

Queer is that no packets are sent., just received.
And if packets cannot be sent , then obviously the request info will not be received.
[ DHCPDISCOVER vs. DHCPOFFER ]

Is there a newer kernel available for Ubuntu 8.04? it is likely the driver is not working corectly yet.

Also by using the full /etc/init.d/networking restart, the specific loading of modprobe -r & modprobe other driver might be undone unless you have blacklisted the r8169 driver, see mentioned article.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 5
  • 4
  • 4
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now