RE: Double Net cards? problem#1 solved


Subject: RE: Double Net cards? problem#1 solved
From: Barry Sparenborg (sparenborgb@hadadycorp.com)
Date: Mon Apr 02 2001 - 07:23:44 MDT


Here is what worked for me under the same situation:

Created a new kernel with no support for the dec (D21143) chip no other card
either. That stopped it from picking it up at boot time. Then setup the
tulip card as you did (modprobe tulip)and put it into a boot script. Now I
only get eth0 (built in interface) and eth1 (farallon 10/100 card) and they
both work.

barry

        -----Original Message-----
        From: Vanja Bucic [SMTP:vanjab@UDel.Edu]
        Sent: Friday, March 30, 2001 6:23 PM
        To: yellowdog-general@lists.yellowdoglinux.com
        Subject: Re: Double Net cards? problem#1 solved

        OK, here what was happening: kernel was seeing one extra card !!!
eth0
        was the BMAC, eth1 was a GHOST ethernet interface, and then after
        manually doing 'modprobe tulip' the kernel would register yet
another
        eth interface - eth2.
        eth2 WORKS!

        Here is what was going on, maybe some of you can explain it to me:

        early in the boot process-
        Mar 30 19:09:50 cosray-g3 kernel: eth0: BMAC at 00:05:02:ad:d9:22
        Mar 30 19:09:50 cosray-g3 kernel: eth1: DC21143 at 0x0400 (PCI bus
0,
        device 14)
        , h/w address 00:00:c5:53:b4:a1,
        Mar 30 19:09:50 cosray-g3 kernel: and requires IRQ24 (provided
by
        PCI BIOS
        ).
        Mar 30 19:09:50 cosray-g3 kernel: de4x5.c:V0.544 1999/5/8
        davies@maniac.ultranet
        .com

        OK. eth1 does not work after this.
        Now I do 'modprobe tulip' -

        Mar 30 19:11:59 cosray-g3 kernel: tulip.c:v0.92 4/17/2000 Written
by
        Donald Becker <becker@scyld.com>
        Mar 30 19:11:59 cosray-g3 kernel:
        http://www.scyld.com/network/tulip.html
        Mar 30 19:11:59 cosray-g3 kernel: The PCI BIOS has not enabled the

        device at 0/112! Updating PCI command 0015->001
        7.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: Digital DS21143 Tulip rev 65
at
        0xdc83e000, 00:00:C5:53:B4:A1, IRQ 24.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: EEPROM default media type
        Autosense.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: Index #0 - Media 10baseT
(#0)
        described by a 21142 Serial PHY (2) block.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: Index #1 - Media
10baseT-FDX
        (#4) described by a 21142 Serial PHY (2) block.

        Mar 30 19:11:59 cosray-g3 kernel: eth2: Index #2 - Media 100baseTx
(#3)
        described by a 21143 SYM PHY (4) block.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: Index #3 - Media
100baseTx-FDX
        (#5) described by a 21143 SYM PHY (4) block.
        Mar 30 19:11:59 cosray-g3 kernel: eth2: Index #4 - Media 100baseTx
(#3)
        described by a 21143 reset method (5) block.

        And eth2 interface is created. Now I do 'ifup eth2' and bingo, it
        works!!!

        here is the result - ifconfig gives me

        eth2 Link encap:Ethernet HWaddr 00:00:C5:53:B4:A1
                   inet addr:128.175.14.23 Bcast:128.175.14.255
        Mask:255.255.255.0
                   UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
                   RX packets:733 errors:0 dropped:0 overruns:0 frame:0
                   TX packets:329 errors:0 dropped:0 overruns:0 carrier:0
                   collisions:0 txqueuelen:100
                   Interrupt:24 Base address:0xe000

        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

        Which is fine. Telnet works, ping works.

        Would somebody explain to me what exactly was going on?

        Thanks.



This archive was generated by hypermail 2a24 : Mon Apr 02 2001 - 07:34:50 MDT