|Rebuilt 5.5 no networking
|Page 1 of 1|
|Author:||steptow [ Fri Jun 11, 2010 1:03 am ]|
|Post subject:||Rebuilt 5.5 no networking|
I have rebuilt my knoppmyth 5.5 backend due to new motherboard/processor/tuner. I performed a standard install.
As a backend it is working except I cannot connect through ethernet outbound or inbound. Relevant information from the backend console
ping -c 2 192.168.1.1 gives
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.4 icmp_seq=1 Destination Host Unreachable
From 192.168.1.4 icmp_seq=2 Destination Host Unreachable
--- 192.168.1.1 ping statistics ---
2 packets transmitted, 0 received, +2 errors, 100% packet loss, time 999ms
, pipe 2
eth0 Link encap:Ethernet HWaddr 00:24:1D:87:42:52
inet addr:192.168.1.4 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::224:1dff:fe87:4252/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:4294967282 overruns:0 frame:0
TX packets:0 errors:0 dropped:80270 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:17 Base address:0xc000
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:1176828 errors:0 dropped:0 overruns:0 frame:0
TX packets:1176828 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:532119630 (507.4 MiB) TX bytes:532119630 (507.4 MiB)
Note that eth0 is UP
# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)
# The loopback interface
# automatically added when upgrading
auto lo eth0
iface lo inet loopback
iface eth0 inet static
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
/sbin/route add default gw 192.168.1.1
SIOCADDRT: File exists
This all looks OK to me
Can anyone help me diagnose the issue. Thanks
|Author:||steptow [ Thu Jun 17, 2010 6:18 pm ]|
|Author:||mihanson [ Thu Jun 17, 2010 7:02 pm ]|
Does /etc/resolv.conf exist and if so, what are it's contents?
|Author:||mythedoff [ Fri Jun 18, 2010 9:02 am ]|
eth0 might have been renamed and if it did then you would have to change to what that is. I had this happen on one of my machines so I use eth2 instead of eth0.
$ dmesg | grep -i eth[0-9]
[ 2.587137] e100: eth0: e100_probe: addr 0xfbfff000, irq 20, MAC addr 00:0c:f1:bc:3f:43
[ 32.765233] udev: renamed network interface eth0 to eth2
[ 33.334570] ADDRCONF(NETDEV_UP): eth2: link is not ready
[ 33.336152] e100: eth2 NIC Link is Up 100 Mbps Full Duplex
[ 33.336411] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
[ 43.448025] eth2: no IPv6 routers present
|Author:||tjc [ Sun Jun 20, 2010 8:41 am ]|
Try running the networking script with the "reset and start over" option. I forget the details but a search through the forums should turn them up. Ah-ha...
|Author:||steptow [ Tue Jun 22, 2010 8:28 am ]|
but that should not be used anyway since I am doing a ping to the ip address
dmesg|grep -i eth[0-9] returns
eth0:RTL8168b/8111b at 0xf.......... IRQ 17
r8169: eth0: link up
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
doing netcardconfig ran through the configuration dialog. I used the following
use DHCP broadcast <no>
IP Address for eth0 192.168.1.4
Network Mask for eth0 255.255.255.0
Broadcast Address for eth0 192.168.1.255
Default Gateway 192.168.1.1
the result was
ifconfig eth0 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255 up
route add default gw 192.168.1.1
SIOCADDRT: File exists
auto lo eth0
Setting Nameserver in /etc/resolve.conf to 192.168.1.1
Looks like the error is in SIOCADDRT. Found may results on a search but cannot yet find a match for the problem I am having.
Any more ideas?
|Author:||tophee [ Tue Jun 22, 2010 9:20 am ]|
Did you say you had new hardware? Actually I'll answer that one myself: yes you did. Have you tried other software with your new system? for example does the latest ubuntu work correctly?
It could be a simple thing like the new hardware is not supported by the kernal in 5.5.
I had this problem initially when I bought a new mobo (in sig) - upgrading to R6 sorted me right out as it's kernal is more up to date.
|Author:||alien [ Wed Jun 23, 2010 12:19 am ]|
NETDEV WATCHDOG: eth0: transmit timed outThat's your problem. I suggest you google "NETDEV WATCHDOG: eth0: transmit timed out".
(Just a guess, but you might first try changing pnp OS settings in your BIOS if you have them.... I think this is an IRQ problem)
|Author:||steptow [ Wed Jul 14, 2010 12:52 am ]|
|Post subject:||LINHES supports the network adapter|
I installed LINHES on a new disk and networking works. So the problem is new hardware not recognized by Knoppmyth 5.5. Now I just have to upgrade everything.
|Page 1 of 1||All times are UTC - 6 hours|
|Powered by phpBB® Forum Software © phpBB Group