[vortex] Dell Latitude C500

[Gavin Tabor]

Andrew Morton wrote:
> 
> Gavin Tabor wrote:
> >
> > Andrew Morton wrote:
> > >
> > > Gavin Tabor wrote:
> > > >
> > > > 3c59x.c 15 Sept00 Donald Becker and others.....
> > > > eth0: 3Com 3c556 10/100 Mini PCI Adapter at 0xd400, 00:04:76:45:f2:d9
> > > > IRQ11
> > > > eth0: Card Bus functions mapped f3ffd800->c8096800 (PCMCIA committee
> > > > brain-damage)
> > > > Internal config register is 80600000, transcievers 0x40
> > > > 8K byte-wide RAM 5:3 Rx:Tx split, MII interface
> > > > MII transceiver found at address 0, status 7809
> > > > Enabling bus-master transmits and whole-frame receives
> > > >
> > > > Does this mean anything?
> > > >
> > >
> > > So far, so good.  More info is needed...  Can you please run the
> > > same test, but try to send some traffic through the interface?
> > >
> > >         ifdown eth0
> >
> > I don't seem to have ifdown, ifup. AFAICT these are Red Hat scripts,
> > which don't seem to exist on SuSE. They act to switch the device on/off,
> > right? Are they things I can download and install, or how should I
> > proceed.
> 
> Ah.  Yes, it's redhat.  You could try `ifconfig eth0 down'.
> But I'm sure there's a script or tool which is used to open and close
> interfaces?
> 
> > >         rmmod 3c59x
> > >         dmesg -n 8
> > >         modprobe 3c59x debug=7
> > >         ifup eth0
> > >         ping some-host-name
> > >
> > > And send the logs?
> >
> > Pardon me for asking a really stupid question - which logs? I've been
> > looking at the files in /var/log, and I can't tell which one you want.
> 
> Normally /var/log/messages - you can tell from the syslog config
> file, normally /etc/syslog.conf

OK .. I think ifconfig eth0 up/down is the way to go. Doing this I get
the
following entry in the /var/log/messages file (everytthing preceeded
with
"Oct 19 16:22:35 strauss kernel:")

3c59x.c 15Sept00 Donal Becker and others...
eth0: 3Com 3c556 10/100 Mini PCI Adapter at 0xd400, 00:04:76:45:f2:d9,
IRQ 11
eth0: CardBus functions mapped f3ffd800->c8090800 (PCMCIA committee
brain-damage).
Internal config register is 80600000, transceivers 0x40.
8K byte-wide RAM 5:3  Rx:Tx split, MII interface
MII transceiver found at address 0, status 782d.
Enabling bus-master transmits and whole-frame receives.
eth0: Initial media type MII
eth0: MII #0 status 782d, link partner capability 40a1, setting
half-duplex.
eth0: vortex_open() InternalConfig 806000000.
eth0: vortex_open() irq 11 media status a880.
eth0: Filling in the Rx ring.
eth0: interrupt, status e401, latency 4, cur_rx 0, dirty_rx 0
eth0: In interrup loop, status e401,
In boomerang_rx(), status e001, rx_status 0000.
Receiving packet size 60 status 803c.
eth0: exiting interrupt, status e000.
eth0: interrupt, status e401, latency 3, cur_rx 1, dirty_rx 1
eth0: In interrupt loop, status e401

It then repeats like that for a very long time : latencies 4,5,3,
cur_rx taking various values up to 105, same for dirty_rx

> 
> > >
> > > Also, are you sure everything is set up right at the IP level?  Please
> > > the console (not logfile) output from:
> > >
> > >         ifup eth0
> > >         ifconfig
> > >         route -n
> > >
> > ifconfig :
> >
> > lo   Link encap : Local Loopback
> >      inet addr : 127.0.0.1  Mask : 255.0.0.0
> >      UP LOOPBACK RUNNING MTU:3924 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:0
> 
> That's the loopback device.  There should be an entry for the
> ethernet device, `eth0'.  The interface hasn't been opened?

ifconfig now gives the following :

eth0  Link encap:Ethernet HWaddr 00:04:76:45:F2:D9
       UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
      RX packets:39613 errors:0 dropped:0 overruns:217 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:100
      Interrupt:11 Base address:0xd400

lo    Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      UP LOOPBACK etc... same now as before

Route -n gives the same as before though.

Gavin

> 
> > route -n :
> >
> > Kernel IP routing table
> > Destination   Gateway   Genmask   Flags   Metric   Ref   Use   Iface
> > 127.0.0.0     0.0.0.0   255.0.0.0 U       0        0     0     lo
> >
> 
> Yup.  The interface needs to be opened.  I'm not sure how
> this is done under Suse.

-- 

Dr. Gavin Tabor
School of Engineering and Computer Science
Department of Engineering
University of Exeter