Re: Ethernet card config - Bering

> From: Donald Becker <[email protected]>
> Date: Mon, 29 Jul 2002 12:27:50 -0400 (EDT)
> ...

>> The BIOS defaulted both cards to the same IRQ.
> 
> This is not a problem with PCI cards.  In ancient times there were a few
> broken SCSI drivers, but those have long since been fixed.

OK.  I let the BIOS set both cards to IRQ 11.

>> # needed by PCI modules
>> pci-scan
> 
> You shouldn't need to list this explicitly.  The PCI scanning and power
> management support is automatically loaded before the rtl8139.o module.

When I take this line out, the output of "ip addr" is:

1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: dummy0: <BROADCAST,NOARP> mtu 1500 qdisc noop
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff

So I put it bsck in.

>> Shortly after boot, the following message is displayed:
>> 
>> eth0: Transmit timeout, status 0c 0005 media 00.
> 
> There should have been other messages before this.
> What is the detection message?

I'm not sure what you mean by detection message (newbie).  Here are the
contents of syslog:

Jul 31 19:54:19 firewall syslogd 1.3-3#31.slink1: restart.
Jul 31 19:54:20 firewall kernel: klogd 1.3-3#31.slink1, log source =
/proc/kmsg started.
Jul 31 19:54:20 firewall kernel: Cannot find map file.
Jul 31 19:54:20 firewall kernel: Loaded 48 symbols from 12 modules.
Jul 31 19:54:20 firewall kernel: Linux version 2.4.18 (root@debian) (gcc
version 2.95.2 20000220 (Debian GNU/Linux)) #4 Sun Jun 9 09:46:15 CEST 2002
Jul 31 19:54:20 firewall kernel: BIOS-provided physical RAM map:
Jul 31 19:54:20 firewall kernel:  BIOS-e801: 0000000000000000 -
000000000009f000 (usable)
Jul 31 19:54:20 firewall kernel:  BIOS-e801: 0000000000100000 -
0000000008000000 (usable)
Jul 31 19:54:20 firewall kernel: On node 0 totalpages: 32768
Jul 31 19:54:20 firewall kernel: zone(0): 4096 pages.
Jul 31 19:54:20 firewall kernel: zone(1): 28672 pages.
Jul 31 19:54:20 firewall kernel: zone(2): 0 pages.
Jul 31 19:54:20 firewall kernel: Kernel command line: BOOT_IMAGE=linux
initrd=initrd.lrp init=/linuxrc root=/dev/ram0 boot=/dev/fd0u1680:msdos
PKGPATH=/dev/fd0u1680
LRP=root,etc,local,modules,ppp,pppoe,shorwall,dnscache,weblet,dhcpd
Jul 31 19:54:20 firewall kernel: Initializing CPU#0
Jul 31 19:54:20 firewall kernel: Detected 59.830 MHz processor.
Jul 31 19:54:20 firewall kernel: Console: colour VGA+ 80x25
Jul 31 19:54:20 firewall kernel: Calibrating delay loop... 119.19 BogoMIPS
Jul 31 19:54:20 firewall kernel: Memory: 126884k/131072k available (864k
kernel code, 3800k reserved, 214k data, 60k init, 0k highmem)
Jul 31 19:54:20 firewall kernel: Dentry-cache hash table entries: 16384
(order: 5, 131072 bytes)
Jul 31 19:54:20 firewall kernel: Inode-cache hash table entries: 8192
(order: 4, 65536 bytes)
Jul 31 19:54:20 firewall kernel: Mount-cache hash table entries: 2048
(order: 2, 16384 bytes)
Jul 31 19:54:20 firewall kernel: Buffer-cache hash table entries: 8192
(order: 3, 32768 bytes)
Jul 31 19:54:20 firewall kernel: Page-cache hash table entries: 32768
(order: 5, 131072 bytes)
Jul 31 19:54:20 firewall kernel: CPU: Before vendor init, caps: 000001bf
00000000 00000000, vendor = 0
Jul 31 19:54:20 firewall kernel: Intel Pentium with F0 0F bug - workaround
enabled. 
Jul 31 19:54:20 firewall kernel: CPU: After vendor init, caps: 000001bf
00000000 00000000 00000000
Jul 31 19:54:20 firewall kernel: CPU:     After generic, caps: 000001bf
00000000 00000000 00000000
Jul 31 19:54:20 firewall kernel: CPU:             Common caps: 000001bf
00000000 00000000 00000000
Jul 31 19:54:20 firewall kernel: CPU: Intel Pentium 75 - 200 stepping 05
Jul 31 19:54:20 firewall kernel: Checking 'hlt' instruction... OK.
Jul 31 19:54:20 firewall kernel: POSIX conformance testing by UNIFIX
Jul 31 19:54:20 firewall kernel: PCI: BIOS32 entry (0xc00fbfe0) in high
memory, cannot use.
Jul 31 19:54:20 firewall kernel: PCI: Using configuration type 1
Jul 31 19:54:20 firewall kernel: PCI: Probing PCI hardware
Jul 31 19:54:20 firewall kernel: Linux NET4.0 for Linux 2.4
Jul 31 19:54:20 firewall kernel: Based upon Swansea University Computer
Society NET3.039 
Jul 31 19:54:20 firewall kernel: Initializing RT netlink socket
Jul 31 19:54:20 firewall kernel: Starting kswapd
Jul 31 19:54:20 firewall kernel: pty: 256 Unix98 ptys configured
Jul 31 19:54:20 firewall kernel: Serial driver version 5.05c (2001-07-08)
with MANY_PORTS SHARE_IRQ DETECT_IRQ SERIAL_PCI enabled
Jul 31 19:54:20 firewall kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A
Jul 31 19:54:20 firewall kernel: Software Watchdog Timer: 0.05, timer
margin: 60 sec 
Jul 31 19:54:20 firewall kernel: block: 128 slots per queue, batch=32
Jul 31 19:54:20 firewall kernel: RAMDISK driver initialized: 16 RAM disks of
4096K size 1024 blocksize
Jul 31 19:54:20 firewall kernel: Floppy drive(s): fd0 is 1.44M
Jul 31 19:54:20 firewall kernel: FDC 0 is a post-1991 82077
Jul 31 19:54:20 firewall kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jul 31 19:54:20 firewall kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Jul 31 19:54:20 firewall kernel: IP: routing cache hash table of 1024
buckets, 8Kbytes 
Jul 31 19:54:20 firewall kernel: TCP: Hash tables configured (established
8192 bind 8192) 
Jul 31 19:54:20 firewall kernel: Linux IP multicast router 0.06 plus PIM-SM
Jul 31 19:54:20 firewall kernel: ip_conntrack version 2.0 (1024 buckets,
8192 max) - 312 bytes per conntrack
Jul 31 19:54:20 firewall kernel: ip_tables: (C) 2000-2002 Netfilter core
team 
Jul 31 19:54:20 firewall kernel: NET4: Unix domain sockets 1.0/SMP for Linux
NET4.0. 
Jul 31 19:54:20 firewall kernel: RAMDISK: Compressed image found at block 0
Jul 31 19:54:20 firewall kernel: Freeing initrd memory: 400k freed
Jul 31 19:54:20 firewall kernel: VFS: Mounted root (minix filesystem).
Jul 31 19:54:20 firewall kernel: Freeing unused kernel memory: 60k freed
Jul 31 19:54:20 firewall kernel: VFS: Disk change detected on device
fd(2,44) 
Jul 31 19:54:20 firewall kernel: rtl8139.c:v1.17 1/28/2002 Donald Becker,
[email protected]. 
Jul 31 19:54:20 firewall kernel:  http://www.scyld.com/network/rtl8139.html
Jul 31 19:54:20 firewall kernel: eth0: D-Link DFE-538TX (RealTek RTL8139) at
0x1000, IRQ 11, 00:50:ba:cc:67:58.
Jul 31 19:54:20 firewall kernel: eth1: RealTek RTL8139C Fast Ethernet at
0x1800, IRQ 11, 00:50:ba:42:c7:b0.
Jul 31 19:54:20 firewall kernel: CSLIP: code copyright 1989 Regents of the
University of California
Jul 31 19:54:20 firewall kernel: HDLC line discipline: version $Revision:
3.3 $, maxframe=4096
Jul 31 19:54:20 firewall kernel: N_HDLC line discipline registered.
Jul 31 19:54:20 firewall kernel: PPP generic driver version 2.4.1
Jul 31 19:54:20 firewall kernel: grsec: time set by (hwclock:25905) UID(0)
EUID(0), parent (S50hwclock:4689) UID(0) EUID(0)
Jul 31 19:54:20 firewall dhcpd: Internet Software Consortium DHCP Server
2.0pl5
Jul 31 19:54:20 firewall dhcpd: Copyright 1995, 1996, 1997, 1998, 1999 The
Internet Software Consortium.
Jul 31 19:54:20 firewall dhcpd: All rights reserved.
Jul 31 19:54:20 firewall dhcpd:
Jul 31 19:54:20 firewall dhcpd: Please contribute if you find this software
useful.
Jul 31 19:54:20 firewall dhcpd: For info, please visit
http://www.isc.org/dhcp-contrib.html
Jul 31 19:54:20 firewall dhcpd:
Jul 31 19:54:20 firewall dhcpd: Listening on
LPF/eth1/00:50:ba:42:c7:b0/192.168.1.0
Jul 31 19:54:20 firewall dhcpd: Sending on
LPF/eth1/00:50:ba:42:c7:b0/192.168.1.0
Jul 31 19:54:20 firewall dhcpd: Sending on   Socket/fallback/fallback-net
Jul 31 19:54:37 firewall root: Shorewall Started
Jul 31 19:54:38 firewall /usr/sbin/cron[28647]: (CRON) INFO (pidfile fd = 3)
Jul 31 19:54:38 firewall /usr/sbin/cron[20782]: (CRON) STARTUP (fork ok)
Jul 31 19:55:19 firewall kernel: eth0: Transmit timeout, status 0d 0004
media 00. 
Jul 31 19:55:19 firewall kernel: eth0: Tx queue start entry 4  dirty entry
0, full. 
Jul 31 19:55:19 firewall kernel: eth0:  Tx descriptor 0 is 0008a03c. (queue
head) 
Jul 31 19:55:19 firewall kernel: eth0:  Tx descriptor 1 is 0008a03c.
Jul 31 19:55:19 firewall kernel: eth0:  Tx descriptor 2 is 0008a03c.
Jul 31 19:55:19 firewall kernel: eth0:  Tx descriptor 3 is 0008a03c.
Jul 31 19:55:19 firewall kernel: eth0: MII #32 registers are: 1100 782d 0000
0000 01e1 45e1 0001 0000.
Jul 31 20:00:01 firewall /USR/SBIN/CRON[16638]: (root) CMD
(/etc/multicron-p)
Jul 31 20:03:22 firewall kernel: VFS: Disk change detected on device fd(2,0)
Jul 31 20:03:57 firewall kernel: VFS: Disk change detected on device fd(2,0)

> What is the packet count when this happens?  ('cat /proc/net/dev/')

The file /proc/net/dev is size zero.

> What does 'mii-diag' report?
> http://www.scyld.com/diag/index.html
> ftp://ftp.scyld.com/pub/diag/

I'll ask that someone on the LEAF list to compile mii-diag for me.

>> I tried one of the D-Link boards with a Linksys board.  In that
>> configuration I could force which board was eth0 and eth1 by the order in
>> which modules were listed in /etc/modules.  I could get either the LAN or
>> the WAN to work (meaning successful pings), but not both at the same time.
> 
> This points to a routing or firewall problem.
> 
> Note that the Linksys card requires a bus-master slot, so if it works
> there is not a PCI slot problem.

I wasn't very clear here.  When I had the D-Link board and the Linksys
boards installed together, I could only get one working - the D-Link board.
By swapping the order the driver modules were listed in /etc/modules, I
could force the boards to swap assignments
    D-Link on eth0 and Linksys on eth1
            vs
    Linksys on eth0 and D-Link on eth1
But always, the interface (eth0 or eth1) assigned to the D-Link board
worked, and the interface assigned to the Linksys board didn't.  This made
me suspect a hardware problem with the Linksys board, but it passed the
diagnostic program that came packaged with the board, and it worked if
installed alone.


Two more data points:

1) I downloaded Freesco for pppoe and ran setup with the 2 D-Link board
configuration.  Freesco only identifies 1 of the 2 boards (i.e. ifconfig has
an entry for eth0, but not for eth1).  The ppp0 interface works (i.e. I can
successfully ping the gateway).

2) I installed 1 of the D-Link boards and an ISA board, and brought the
system up with Freesco.  Both interfaces seem to work - yea.

I would like to get the ISA board back to its other application.  Any help
debugging the 2 PCI configuration is appreciated.

DPD