from your /etc/networks/interfaces, I can see that there is something
(funny) renaming your eth1 to eth2 and this will not allow it to work.
It is important to know whether eth0 is working fine.Since it is a LAN
card, I think you can check whether pinging 192.168.0.254 from the LAN
computers will yield results. Right now I cannot guess off-head what is
doing the renaming the NiC card from eth1 to eth2 right now but I think
I can get some time on it but from your side, you should try to look at
the line # [   11.671418] udevd[441]: renamed network interface eth1 to
eth2#. As a question, why do you put your DNS configs in the interface
file? Thought that info is supposed to be in the resolv.conf file? yet
more, the interface file is still confusing although this cannot stop it
from working, but I think the properties of eth0 should be under auto
eth0 and those of eth1 should go under auto eth1 not vice versa. 
-- 
Kind regards;
KTM
+256752602550||+256782062708
"Mother of God-Pray for us sinners"


On Mon, 2013-07-01 at 10:11 +0300, Muganwa Michael wrote:
> Hi Thomas,
> 
>  below is the output for dmesg
> 
> root@(none):~# dmesg |grep eth
> [    0.153799] HP Compaq Laptop series board detected. Selecting
> BIOS-method for reboots.
> [    0.280509] ACPI Error: Method parse/execution failed
> [\_SB_.PCI0._OSC] (Node f54261e0), AE_ALREADY_EXISTS
> (20110623/psparse-536)
> [    0.280528] ACPI: Marking method _OSC as Serialized because of
> AE_ALREADY_EXISTS error
> [    0.285444] ACPI Error: Method parse/execution failed
> [\_SB_.PCI0._OSC] (Node f54261e0), AE_ALREADY_EXISTS
> (20110623/psparse-536)
> [    0.285624] ACPI Error: Method parse/execution failed
> [\_SB_.PCI0._OSC] (Node f54261e0), AE_ALREADY_EXISTS
> (20110623/psparse-536)
> [    0.299126] i2c-core: driver [aat2870] using legacy suspend method
> [    0.299131] i2c-core: driver [aat2870] using legacy resume method
> [    1.366562] tg3 0000:40:00.0: eth0: Tigon3 [partno(BCM95751) rev
> 4001] (PCI Express) MAC address 00:17:a4:19:c3:46
> [    1.366572] tg3 0000:40:00.0: eth0: attached PHY is 5750
> (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[0])
> [    1.366580] tg3 0000:40:00.0: eth0: RXcsums[1] LinkChgREG[0]
> MIirq[0] ASF[0] TSOcap[1]
> [    1.366587] tg3 0000:40:00.0: eth0: dma_rwctrl[76180000]
> dma_mask[64-bit]
> [    1.417492] skge 0000:05:09.0: eth1: addr 00:19:5b:fa:b0:a8
> [   10.802497] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   10.802513] ADDRCONF(NETDEV_UP): eth1: link is not ready
> [   11.475544] ADDRCONF(NETDEV_UP): eth0: link is not ready
> [   11.671418] udevd[441]: renamed network interface eth1 to eth2
> [   13.179068] tg3 0000:40:00.0: eth0: Link is up at 100 Mbps, full
> duplex
> [   13.179074] tg3 0000:40:00.0: eth0: Flow control is off for TX and
> off for RX
> [   13.179224] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
> [   23.648123] eth0: no IPv6 routers present
> root@(none):~# 
> 
> 
>  and /etc/network/interfaces reads
> 
> root@(none):~# cat /etc/network/interfaces
> 
> 
> auto lo
> iface lo inet loopback
> 
> # The LAN network interface 
> auto eth1
> iface eth0 inet static
> address 192.168.0.254
> network 192.168.0.0
> netmask 255.255.255.0
> broadcast 192.168.0.255
> 
> dns-nameservers 41.202.229.140 41.202.229.144
> 
> 
> 
> 
> 
> # The INTERNET interface 
> auto eth0
> iface eth1 inet static
> address 1**.1**.*.**2
> netmask 255.255.255.252
> gateway 1**.1**.**.***
> broadcast 1**.1**.**.255
> 
> 
> 
> 
> Regards,
> 
> 
> Michael Muganwa
> 
> 
> 
> 
> On Mon, Jul 1, 2013 at 9:36 AM, Kizito Thomas <[email protected]>
> wrote:
>         How does the /etc/network/interfaces read? How about dmesg in
>         particular
>         greping 'eth'
>         --
>         Kind regards;
>         KTM
>         +256752602550||+256782062708
>         "Mother of God-Pray for us sinners"
>         
>         
>         On Mon, 2013-07-01 at 09:05 +0300, Muganwa Michael wrote:
>         > Good morning colleagues,
>         >
>         >   I hope you all had a wonderful weekend. I have this
>         gateway running
>         > ubuntu 12.04 that has been working well for a couple of
>         months but
>         > yesterday,I got to office and its DLINK PCI ethernet card
>         was down. I
>         > restarted the server and the interface came up but six hours
>         later it
>         > did the same thing. I restarted it again but this time it
>         didnt come
>         > up. I entered "sudo ifconfig eth1 up" but it said device not
>         found. I
>         > then did an "lshw -c network" and it shows that that device
>         is
>         > disabled plus its logical name has changed from eth1 to
>         eth2. Any help
>         > is appreciated. By the way,I opened the machine up,made sure
>         the card
>         > was firm in its slot and reset the bios but all that didnt
>         help
>         > either. The output for the two command is pasted below
>         >
>         >
>         > root@(none):~# ifconfig eth1 up
>         > eth1: ERROR while getting interface flags: No such device
>         > root@(none):~# ping www.yahoo.com
>         > ping: unknown host www.yahoo.com
>         > root@(none):~# lshw -c network
>         >   *-network
>         >        description: Ethernet interface
>         >        product: NetXtreme BCM5751 Gigabit Ethernet PCI
>         Express
>         >        vendor: Broadcom Corporation
>         >        physical id: 0
>         >        bus info: pci@0000:40:00.0
>         >        logical name: eth0
>         >        version: 01
>         >        serial: 00:17:a4:19:c3:46
>         >        size: 100Mbit/s
>         >        capacity: 1Gbit/s
>         >        width: 64 bits
>         >        clock: 33MHz
>         >        capabilities: pm vpd msi pciexpress bus_master
>         cap_list
>         > ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt
>         1000bt-fd
>         > autonegotiation
>         >        configuration: autonegotiation=on broadcast=yes
>         driver=tg3
>         > driverversion=3.121 duplex=full firmware=5751-v3.29a
>         ip=192.168.0.254
>         > latency=0 link=yes multicast=yes port=twisted pair
>         speed=100Mbit/s
>         >        resources: irq:17 memory:f0400000-f040ffff
>         >   *-network DISABLED
>         >        description: Ethernet interface
>         >        product: DGE-530T Gigabit Ethernet Adapter (rev 11)
>         >        vendor: D-Link System Inc
>         >        physical id: 9
>         >        bus info: pci@0000:05:09.0
>         >        logical name: eth2
>         >        version: 11
>         >        serial: 00:19:5b:fa:b0:a8
>         >        capacity: 1Gbit/s
>         >        width: 32 bits
>         >        clock: 66MHz
>         >        capabilities: pm vpd bus_master cap_list rom ethernet
>         physical
>         > tp 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd
>         autonegotiation
>         >        configuration: autonegotiation=on broadcast=yes
>         driver=skge
>         > driverversion=1.14 firmware=N/A latency=32 link=no
>         maxlatency=31
>         > mingnt=23 multicast=yes port=twisted pair
>         >        resources: irq:18 memory:f0500000-f0503fff
>         > ioport:3000(size=256) memory:60000000-6001ffff
>         > root@(none):~#
>         >
>         >
>         >
>         > Regards,
>         >
>         > Michael Muganwa
>         >
>         
>         > _______________________________________________
>         > The Uganda Linux User Group: http://linux.or.ug
>         >
>         > Send messages to this mailing list by addressing e-mails to:
>         [email protected]
>         > Mailing list archives:
>         http://www.mail-archive.com/[email protected]/
>         > Mailing list settings: http://kym.net/mailman/listinfo/lug
>         > To unsubscribe: http://kym.net/mailman/options/lug
>         >
>         > The Uganda LUG mailing list is generously hosted by INFOCOM:
>         http://www.infocom.co.ug/
>         >
>         > The above comments and data are owned by whoever posted them
>         (including attachments if any). The mailing list host is not
>         responsible for them in any way.
>         
>         _______________________________________________
>         The Uganda Linux User Group: http://linux.or.ug
>         
>         Send messages to this mailing list by addressing e-mails to:
>         [email protected]
>         Mailing list archives:
>         http://www.mail-archive.com/[email protected]/
>         Mailing list settings: http://kym.net/mailman/listinfo/lug
>         To unsubscribe: http://kym.net/mailman/options/lug
>         
>         The Uganda LUG mailing list is generously hosted by INFOCOM:
>         http://www.infocom.co.ug/
>         
>         The above comments and data are owned by whoever posted them
>         (including attachments if any). The mailing list host is not
>         responsible for them in any way.
> 
> 
> _______________________________________________
> The Uganda Linux User Group: http://linux.or.ug
> 
> Send messages to this mailing list by addressing e-mails to: [email protected]
> Mailing list archives: http://www.mail-archive.com/[email protected]/
> Mailing list settings: http://kym.net/mailman/listinfo/lug
> To unsubscribe: http://kym.net/mailman/options/lug
> 
> The Uganda LUG mailing list is generously hosted by INFOCOM: 
> http://www.infocom.co.ug/
> 
> The above comments and data are owned by whoever posted them (including 
> attachments if any). The mailing list host is not responsible for them in any 
> way.

_______________________________________________
The Uganda Linux User Group: http://linux.or.ug

Send messages to this mailing list by addressing e-mails to: [email protected]
Mailing list archives: http://www.mail-archive.com/[email protected]/
Mailing list settings: http://kym.net/mailman/listinfo/lug
To unsubscribe: http://kym.net/mailman/options/lug

The Uganda LUG mailing list is generously hosted by INFOCOM: 
http://www.infocom.co.ug/

The above comments and data are owned by whoever posted them (including 
attachments if any). The mailing list host is not responsible for them in any 
way.

Reply via email to