Re: Netgear FA511 on RedHat 7.3

Jared Warren <[email protected]> 16 May 2003 15:44:56 -0500
Newsgroups gmane.linux.drivers.tulip.general
Message-ID <1053117894.23225.133.camel@linuxws1>
> First, verify that 'mii-diag eth1' works with the device -- it should
> (and will not crash the machine).
> 

[root@linuxlt /tmp]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:00:F0:64:6E:B2
          inet addr:10.10.15.155  Bcast:10.10.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:712 errors:0 dropped:0 overruns:0 frame:0
          TX packets:160 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:61330 (59.8 Kb)  TX bytes:14817 (14.4 Kb)
          Interrupt:11 Base address:0xf000

eth1      Link encap:Ethernet  HWaddr 00:10:7A:69:94:71
          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:10 Base address:0x4000

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:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4200 (4.1 Kb)  TX bytes:4200 (4.1 Kb)

[root@linuxlt /tmp]# mii-diag eth1
Basic registers of MII PHY #1:  1100 786d 001d 2411 05e1 0021 0004 2001.
 Basic mode control register 0x1100: Auto-negotiation enabled.
 You have link beat, and everything is working OK.
 Your link partner is generating 10baseT link beat  (no
autonegotiation).
   End of basic transceiver information.

> These debugging steps are difficult because of the immediate machine
> lock-up.  You'll be rebooting a lot.
> My guess is that either the IRQ or bus-master configuration on the
> CardBus bridge is flawed.

> Do not use X windows for debugging.  The kernel will (hopefully) emit a
> crash message to the text console, and that message will identify
> exactly what went wrong.  You may have to disable syslog and enable
> console logging.

With kern.* sent to /dev/console in syslog.conf, I don't see anything on
the console between when I do ifconfig eth1 up and the lockup (most of
the time, I don't even get my command prompt back before I lock up).

> Try another CardBus (no 16 bit PCMCIA) card.  Preferably one that uses
> IRQs but is not a bus master.

I only have one other card.  It's packaged as a "Hawking Technology
PN672TX," but is identified by card services as a "Linksys EtherFast
PCMPC200 v2" - is this one worth testing with?  I've tried just sticking
it in and seeing if it works, but didn't even get anything in ifconfig
-a for eth1 after I booted with it.  What other output can I send you
from this test?

> Try an older or newer kernel, to get a different version of the CardBus
> configuration code.

Any suggested versions to try? 

I don't know if this is worth mentioning, but with the Netgear card, I
only hear the "high" PCMCIA beep at boot.  With the Hawking's Card I
hear both beeps (but still have the symptom above).  With either card,
if I insert or remove the card with the system running, I get a hard
lock. (These may be unrelated to the problem, I don't know).

Thanks again for your help!
jared

-- 
Jared Warren
Adventa Control Technologies
972.543.1690

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip