Jump to content

can't get online

jkroon

By jkroon
in Networking

 Share

Recommended Posts

jkroon New Here

jkroon

Posted
Posted

:help: I have a Systemboard 333 mobo with built-in NIC, plus I added RealTek, then later Siemens,10/100 PCI NICs along the way, all with the same result that I can't get online.

 

When the system boots, it pauses for a long while when trying to start the NICs, then says zcip[708] retrieved address 127.255.255.255 for eth0:9. Then startup continues and MDK finishes loading, but I cannot get onto the ineternet, and my router is unreachable when I ping it.

 

I have tried the MCC both to configure static and dynamic adresses (the DLink914+ router has DHCP enabled), plus I have tried in a terminal to configure both static and dynamic addresses with ifconfig and route add. In all cases I get the same result.

 

Below is one example using a static IP...

 

Any ideas how to get connected?

 

root@localhost mark]# ifconfig

eth0 Link encap:Ethernet HWaddr 00:50:FC:90:64:D8

UP BROADCAST RUNNING 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:100

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:10 Base address:0xaf00

 

eth0:9 Link encap:Ethernet HWaddr 00:50:FC:90:64:D8

inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Interrupt:10 Base address:0xaf00

 

eth1 Link encap:Ethernet HWaddr 00:0D:87:4C:70:37

inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0

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:100

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:5 Base address:0xd800

 

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:118 errors:0 dropped:0 overruns:0 frame:0

TX packets:118 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:7624 (7.4 Kb) TX bytes:7624 (7.4 Kb)

 

[root@localhost mark]# netstat -r

Kernel IP routing table

Destination Gateway Genmask Flags MSS Window irtt Iface

192.168.0.0 * 255.255.255.0 U 0 0 0 eth1

127.0.0.0 * 255.0.0.0 U 0 0 0 lo

default 192.168.0.1 0.0.0.0 UG 0 0 0 eth1

 

[root@localhost mark]# netstat -i

Kernel Interface table

Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg

eth0 1500 0 0 0 0 0 0 0 0 0 BMRU

eth0:9 1500 0 - no statistics available - BMRU

eth1 1500 0 0 0 0 0 0 0 0 0 BMU

lo 16436 0 262 0 0 0 262 0 0 0 LRU

Link to comment
Share on other sites
roland MUB Addict

roland

Posted
Posted

first the obvious: disable any firewall (MCC->DrakeFirewall) if any.

retry.

if not better, try running DrakeGW (internet sharing) it can clean up all and set everyting properly. Be aware I'm not 100% sure of that, it will install a lot of things (Shorewall, bind, DHCP server) and it can be difficult to restore to the original state.

At least it's what I did and it worked ( I needed internet sharing anyway)

 

roland

Link to comment
Share on other sites
jkroon New Here

jkroon

Posted
  • Author
Posted

Thanks for the ideas. I do not have a firewall running in Mandrake. I appreciate your caveat on the second approach, and think that I will hold out to see if there are other thoughts as to what is happening.

 

I have done some more exploring and find no interrupt conflicts (see below). Also, when booting Mandrake 9.2, when it tries to fire up eth0, after a long pause it instead launches dcip. This is then followed by several modprobe commands being issued, and finally an address (127.255.255.255) is "siezed", which is followed by the generation during startup of the eth0:9 lines below.

 

It was after this that I tried 3 other NICs of different manufacture, eventually disabling the built-in NIC as well in various combinations. All efforts yielded the same result.

 

Then I tried to assign a static address, which displays ok in the ifconfig output, but no communication is occuring with my router.

 

I then created another partition on my hard drive and installed Knoppix to it, with precisely the same results. Then I loaded a gentoo rescue-type CD and that worked (from the CD, not loaded onto the hard drive). I can get online, ping the router, etc.

 

Does anyone know what would launch dcip during startup? Is this a system function that runs if DHCP assignment fails? Are the modprobes a part of the dcip script somehow? And what is being "siezed"?

 

Thanks,

Joel

 

[root@localhost mark]# lspcidrake -v

unknown : VIA Technologies Inc|CPU to PCI Bridge [bRIDGE_HOST] (vendor:1106 device:3205 subv:1106 subd:0000)

unknown : VIA Technologies Inc|PCI-to-PCI Bridge (AGP 2.0/3.0) [bRIDGE_PCI] (vendor:1106 device:b198)

8139too : Realtek|RTL-8139 [NETWORK_ETHERNET] (vendor:10ec device:8139)

usb-uhci : VIA Technologies|VT82C586B USB [sERIAL_USB] (vendor:1106 device:3038)

usb-uhci : VIA Technologies|VT82C586B USB [sERIAL_USB] (vendor:1106 device:3038)

usb-uhci : VIA Technologies|VT82C586B USB [sERIAL_USB] (vendor:1106 device:3038)

ehci-hcd : VIA Technologies Inc|VT8235 USB Enhanced Controller [sERIAL_USB] (vendor:1106 device:3104)

unknown : VIA Technologies Inc|VT8233A PCI to ISA Bridge [bRIDGE_ISA] (vendor:1106 device:3177 subv:1106 subd:0000)

unknown : VIA Technologies|VT82C586 IDE [Apollo] [sTORAGE_IDE] (vendor:1106 device:0571)

snd-via82xx : VIA Technologies|VT8233 [AC97 Audio Controller] [MULTIMEDIA_AUDIO] (vendor:1106 device:3059 subv:1106 subd:4161)

via-rhine : VIA Technologies|VT6102 [Rhine II 10/100] [NETWORK_ETHERNET] (vendor:1106 device:3065 subv:1106 subd:0102)

unknown : unknown (1106/7205/1106/0000) [DISPLAY_VGA]

[root@localhost mark]# dmesg | grep eth

eth0: RealTek RTL8139 Fast Ethernet at 0xdee0af00, 00:50:fc:90:64:d8, IRQ 10

eth0: Identified 8139 chip type 'RTL-8139C'

eth1: VIA VT6102 Rhine-II at 0xd800, 00:0d:87:4c:70:37, IRQ 5.

eth1: MII PHY found at address 1, status 0x7869 advertising 05e1 Link 45e1.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

NETDEV WATCHDOG: eth0: transmit timed out

eth0: Tx queue start entry 4 dirty entry 0.

eth0: Tx descriptor 0 is 00002000. (queue head)

eth0: Tx descriptor 1 is 00002000.

eth0: Tx descriptor 2 is 00002000.

eth0: Tx descriptor 3 is 00002000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

eth0: Promiscuous mode enabled.

device eth0 entered promiscuous mode

device eth0 left promiscuous mode

eth1: Setting full-duplex based on MII #1 link partner capability of 45e1.

NETDEV WATCHDOG: eth0: transmit timed out

eth0: Tx queue start entry 4 dirty entry 0.

eth0: Tx descriptor 0 is 00002000. (queue head)

eth0: Tx descriptor 1 is 00002000.

eth0: Tx descriptor 2 is 00002000.

eth0: Tx descriptor 3 is 00002000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

NETDEV WATCHDOG: eth1: transmit timed out

eth1: Transmit timed out, status 0003, PHY status 786d, resetting...

eth1: Setting full-duplex based on MII #1 link partner capability of 45e1.

eth0: Promiscuous mode enabled.

device eth0 entered promiscuous mode

device eth0 left promiscuous mode

eth0: Promiscuous mode enabled.

device eth0 entered promiscuous mode

device eth0 left promiscuous mode

NETDEV WATCHDOG: eth0: transmit timed out

eth0: Tx queue start entry 4 dirty entry 0.

eth0: Tx descriptor 0 is 00002000. (queue head)

eth0: Tx descriptor 1 is 00002000.

eth0: Tx descriptor 2 is 00002000.

eth0: Tx descriptor 3 is 00002000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

eth0: Promiscuous mode enabled.

device eth0 entered promiscuous mode

device eth0 left promiscuous mode

NETDEV WATCHDOG: eth0: transmit timed out

eth0: Tx queue start entry 4 dirty entry 0.

eth0: Tx descriptor 0 is 00002000. (queue head)

eth0: Tx descriptor 1 is 00002000.

eth0: Tx descriptor 2 is 00002000.

eth0: Tx descriptor 3 is 00002000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

eth0: Setting half-duplex based on auto-negotiated partner ability 0000.

[root@localhost mark]# ifconfig

eth0 Link encap:Ethernet HWaddr 00:50:FC:90:64:D8

inet addr:192.168.0.120 Bcast:192.168.0.255 Mask:255.255.255.0

UP BROADCAST RUNNING 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:100

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:10 Base address:0xaf00

 

eth0:9 Link encap:Ethernet HWaddr 00:50:FC:90:64:D8

inet addr:127.255.255.255 Bcast:127.255.255.255 Mask:255.0.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

Interrupt:10 Base address:0xaf00

 

eth1 Link encap:Ethernet HWaddr 00:0D:87:4C:70:37

inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:0 errors:0 dropped:3809 overruns:0 frame:0

TX packets:0 errors:1 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:100

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

Interrupt:5 Base address:0xd800

 

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

UP LOOPBACK RUNNING MTU:16436 Metric:1

RX packets:162 errors:0 dropped:0 overruns:0 frame:0

TX packets:162 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:10290 (10.0 Kb) TX bytes:10290 (10.0 Kb)

 

[root@localhost mark]# cat /proc/interrupts

CPU0

0: 358348 IO-APIC-edge timer

1: 2004 IO-APIC-edge keyboard

2: 0 XT-PIC cascade

5: 0 XT-PIC eth1

8: 1 IO-APIC-edge rtc

9: 0 XT-PIC VIA8233

10: 0 XT-PIC eth0

12: 13369 IO-APIC-edge PS/2 Mouse

14: 16900 IO-APIC-edge ide0

15: 155 IO-APIC-edge ide1

NMI: 0

LOC: 358303

ERR: 0

MIS: 0

[root@localhost mark]#

Link to comment
Share on other sites
pmpatrick Mandriva Guru

pmpatrick

Posted
Posted

One longshot you can try. This happened not infrequently in 9.1. The network startup would hang unless you passed the "noapic" option at boot. To test, reboot and as soon as you see the lilo screen, hit the Esc key. That will take you to a boot prompt where you should type "linux noapic" w/o quotes. Then test to see if you can get one of your nics working.

 

The other obvious thing is to check your cabling to the router just to eliminate that.

 

Also, if you have a router, why are you running two nics? I assume you tried it because you couldn't get the onboard nic to work; what kind is it? Configuring two nics has never worked for me with mcc. I always wind up hand configuring the network interfaces with two nics. Also, please post your /etc/modules.conf file and any "ifcfg-ethx" files in /etc/sysconfig/network-scripts. There should be one for eth0 and eth1.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
 Share
Go to topic listing
×
×
  • Create New...