Re: new to linux rh 9 - ethernet card won't work
From: 2boxers (2boxers_at_comast_dot_net)
Date: 11/23/03
- Next message: H. S.: "Re: what do I need to do to get fedora to play an mp3 file?"
- Previous message: GregM: "Re: mounting an ntfs partition RH9"
- In reply to: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Next in thread: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Reply: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sun, 23 Nov 2003 02:21:05 -0500
On Sat, 22 Nov 2003 22:22:42 -0500, "bently" <bently@sympatico.ca>
wrote:
>Sorry about the first post - it was pretty vague. I have found some more
>info regarding this problem. RH 9 picked the tulip module for my Intel card
>as it was based on a DEC chip.
Are you able to physically look at the network card and see if the
kernel picked the correct driver for it? Chances are it did, but it
never hurts to make sure. The kernel has more than one version of the
DEC chip drivers. You may need to compile a new kernel and modules
and take control of the selection of which module is built and used
for your NIC.
>During system startup the link led on the
>card briefly comes on but goes off almost right away. RH 9 thinks the card
>is operational. I can ping it and ifconfig eth0 gives the following info
Well, the requirements for binding TCP/IP have been met since a module
loaded, but the absense of an identifiable tranceiver explains the
continuous RX errors.
Being able to ping the IP address that is on the local host only tests
the TCP/IP stack. You really aren't testing the card until you can
ping a host outside your system.
>
>eth0 Link encap:Ethernet HWaddr 00:08:C7:63:59:2B
> inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:1934 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:11 Base address:0x9000
This means the driver for the card is loaded, but it doesn't mean it
is working. In this state, the equivalent in Windows would be this
device having an exclamation point in the device manager. If no
tranceiver is detected then there can be no communications. It may be
possible to manually set the tranceiver type for that NIC, but it is
unlikely that will fix the problem since it was not autodetected.
>
>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:43637 errors:0 dropped:0 overruns:0 frame:0
> TX packets:43637 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:2979440 (2.8 Mb) TX bytes:2979440 (2.8 Mb)
>
>also this is the startup log
-snip-
>Nov 22 17:58:47 bently kernel: usb.c: registered new driver hub
>Nov 22 17:58:47 bently kernel: usb-uhci.c: $Revision: 1.275 $ time 17:59:01
>Mar 13 2003
>Nov 22 17:58:47 bently kernel: usb-uhci.c: High bandwidth mode enabled
>Nov 22 17:58:47 bently kernel: PCI: Found IRQ 11 for device 00:14.2
>Nov 22 17:58:47 bently kernel: PCI: Sharing IRQ 11 with 00:12.0
>Nov 22 17:58:47 bently kernel: usb-uhci.c: USB UHCI at I/O 0x2880, IRQ 11
>Nov 22 17:58:47 bently kernel: usb-uhci.c: Detected 2 ports
>Nov 22 17:58:47 bently kernel: usb.c: new USB bus registered, assigned bus
>number 1
>Nov 22 17:58:47 bently kernel: hub.c: USB hub found
>Nov 22 17:58:47 bently kernel: hub.c: 2 ports detected
>Nov 22 17:58:47 bently apmd[2255]: Charge: * * * (-1% unknown)
>Nov 22 17:58:47 bently kernel: usb-uhci.c: v1.275:USB Universal Host
>Controller Interface driver
>Nov 22 17:58:48 bently kernel: usb.c: registered new driver hiddev
>Nov 22 17:58:48 bently kernel: usb.c: registered new driver hid
>Nov 22 17:58:48 bently kernel: hid-core.c: v1.8.1 Andreas Gal, Vojtech
>Pavlik <vojtech@suse.cz>
>Nov 22 17:58:48 bently kernel: hid-core.c: USB HID support drivers
>Nov 22 17:58:48 bently kernel: mice: PS/2 mouse device common for all mice
>Nov 22 17:58:48 bently kernel: hub.c: new USB device 00:14.2-1, assigned
>address 2
>Nov 22 17:58:48 bently kernel: hub.c: USB hub found
>Nov 22 17:58:48 bently kernel: hub.c: 4 ports detected
Note USB on IRQ 11.
-snip-
>Nov 22 17:58:49 bently kernel: ohci1394: $Rev: 693 $ Ben Collins
><bcollins@debian.org>
>Nov 22 17:58:49 bently kernel: PCI: Found IRQ 11 for device 00:13.0
>Nov 22 17:58:50 bently kernel: PCI: Sharing IRQ 11 with 01:00.0
>Nov 22 17:58:50 bently kernel: ohci1394_0: OHCI-1394 1.0 (PCI): IRQ=[11]
>MMIO=[41300000-413007ff] Max Packet=[2048]
>Nov 22 17:58:50 bently kernel: ieee1394: SelfID completion called outside of
>bus reset!
Note Firewire interface on IRQ 11.
>Nov 22 17:58:50 bently kernel: parport0: PC-style at 0x378
>[PCSPP,TRISTATE,EPP]
>Nov 22 17:58:50 bently kernel: ip_tables: (C) 2000-2002 Netfilter core team
>Nov 22 17:58:50 bently kernel: Linux Tulip driver version 0.9.15-pre12 (Aug
>9, 2002)
>Nov 22 17:58:50 bently kernel: PCI: Found IRQ 11 for device 00:12.0
>Nov 22 17:58:50 bently kernel: PCI: Sharing IRQ 11 with 00:14.2
>Nov 22 17:58:51 bently kernel: tulip0: EEPROM default media type Autosense.
>Nov 22 17:58:51 bently kernel: tulip0: Index #0 - Media AUI (#18) described
>by a 21142 Serial PHY (2) block.
>Nov 22 17:58:51 bently kernel: tulip0: Index #1 - Media 10baseT (#0)
>described by a 21142 Serial PHY (2) block.
>Nov 22 17:58:51 bently kernel: tulip0: Index #2 - Media 10baseT-FDX (#4)
>described by a 21142 Serial PHY (2) block.
>Nov 22 17:58:51 bently kernel: tulip0: Index #3 - Media MII (#11) described
>by a 21142 MII PHY (3) block.
>Nov 22 17:58:51 bently kernel: tulip0: ***WARNING***: No MII transceiver
>found!
>Nov 22 17:58:51 bently kernel: eth0: Digital DS21143 Tulip rev 65 at
>0xd08b9000, 00:08:C7:63:59:2B, IRQ 11.
Note NIC on IRQ 11.
All PCI devices are being shared to IRQ 11. Normally I would not
consider this to be an issue, but since it is a Compaq, I would try
going into the BIOS and disable the USB interface temporarily, and
perhaps also disable or unplug the Firewire.
I recall on more than one occasion having add-on NICS fail to work on
Compaq computers until you ease the BIOS into properly assigning
resources. These are some of the computers that coined the term "Plug
and Pray"
1) Your tulip driver is 0.9.15-pre12 The first thing I would do is
look this driver up on google and make sure that it covers the chipset
on your Ethernet card. Getting the chipset is as easy as taking the
case cover off and looking at it.
2) If the driver is the correct one, then you may need to still switch
to an alternate driver in the kernel. As mentioned above, more than
one driver exists for DEC. Compatibility is the reason. If I recall,
the different drivers had something to do with PCI shared memory
registers.
3) Try freeing up some resources for the card by disabling USB and the
Firewire interface, just temporarily for diagnostics. It seems that
the kernel is successfully enumerating devices on the PCI bus, but it
might be able to do this still even if there were an IRQ conflict.
However, an IRQ conflict would prevent there from being
communications. Communications for this card may be necessary to
identify the tranceiver. Perhaps pulling the card out and trying a
different PCI slot. Sometimes this causes the BIOS to reassign
resources.
4) You may need to add kernel command line parameter which forces a
particular tranceiver to be used. I personally do not like having to
do this. It should be automatic.
You may have mentioned this before. Did you say the card was working
with a different OS loaded?
PNP BIOSs can be strange beasts. Their strength is in when you dont
have to use jumpers to set resources, but their weakness are
frightfully a larger negative than having to use jumpers. Sometimes a
BIOS refuses to properly assign resources to a card. When this
happens, you have to try and get it to. One way to do this is remove
all cards and install them 1 at a time until all cards are working
properly, or until you identify which card is causing the conflict.
I hope this helps. Let us know how you make out.
Charles
- Next message: H. S.: "Re: what do I need to do to get fedora to play an mp3 file?"
- Previous message: GregM: "Re: mounting an ntfs partition RH9"
- In reply to: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Next in thread: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Reply: bently: "Re: new to linux rh 9 - ethernet card won't work"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
