[tulip] ANA 6944A/TX weird after testing it with win2k and then going back to Linux

William Harrington wwh20610@cmsu2.cmsu.edu
Tue Dec 18 01:17:01 2001


This is a multi-part message in MIME format.

------=_NextPart_000_001B_01C18759.769945C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

   Having a bit of a problem here.  The card was in the same slot, no =
configuration differences, probably the only thing that changed was the =
IRQ's the interfaces were using.  Before I was goofing around with =
win2k, I had a successful installation of slackware with 2.4.16 kernel =
using the de4x5.o module for the DEC 21140, and I had 4 3c905c's along =
with it (each running their own subnets).  I installed win2k and it =
ended up seeing it as an intel 21140 of course wasn't working, nothing =
was working..... now when I go back to Linux, the card isn't working =
right.  Now either something was changed on the card itself, which I =
suspect, or something else is happening.  When I insmod de4x5 this is =
what is in the message console:

eth0: DC21140 at 0xd000 (PCI bus 2, device 4), h/w address =
00:00:d1:1e:7a:54, and requires IRQ10 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
eth1: DC21140 at 0xd000 (PCI bus 2, device 5), h/w address =
00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
eth2: DC21140 at 0xd000 (PCI bus 2, device 6), h/w address =
00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com
eth3: DC21140 at 0xd000 (PCI bus 2, device 7), h/w address =
00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI BIOS).
de4x5.c:V0.546 2001/02/22 davies@maniac.ultranet.com

I can run dhcpcd on eth0 and get an ip and get out onto the net just =
fine.  If I do dhcpcd on either of the other interfaces I get nothing.  =
I can't figure out why the last 3 interfaces are getting the same h/w =
address.  It is baffling me.  Maybe I"m missing something I should have =
in the kernel, but I don't think so.  Is there something I need to write =
to the ANA-6944A/TX to get the eeprom back to where it should be.  When =
I use the tulip.o I each interface gets a different h/w address, but I =
can't use dhcpcd to get ip's on the last 3 as well. Here is the tulip =
information:

Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)

tulip0: EEPROM default media type Autosense.

tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) =
block.

tulip0: MII transceiver #1 config 3100 status 7849 advertising 0101.

tulip0: Advertising 01e1 on PHY 1, previously advertising 0101.

eth0: Digital DS21140 Tulip rev 34 at 0xd000, 00:00:D1:1E:7A:54, IRQ 10.

tulip1: Controller 1 of multiport board.

tulip1: EEPROM default media type Autosense.

tulip1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) =
block.

tulip1: MII transceiver #1 config 3100 status 7849 advertising 0101.

tulip1: Advertising 01e1 on PHY 1, previously advertising 0101.

eth1: Digital DS21140 Tulip rev 34 at 0xd400, EEPROM not present, =
00:00:D1:1E:7A:55, IRQ 10.

tulip2: Controller 2 of multiport board.

tulip2: EEPROM default media type Autosense.

tulip2: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) =
block.

tulip2: MII transceiver #1 config 3100 status 7849 advertising 0101.

tulip2: Advertising 01e1 on PHY 1, previously advertising 0101.

eth2: Digital DS21140 Tulip rev 34 at 0xd800, EEPROM not present, =
00:00:D1:1E:7A:56, IRQ 10.

tulip3: Controller 3 of multiport board.

tulip3: EEPROM default media type Autosense.

tulip3: Index #0 - Media MII (#11) described by a 21140 MII PHY (1) =
block.

tulip3: MII transceiver #1 config 3100 status 7849 advertising 0101.

tulip3: Advertising 01e1 on PHY 1, previously advertising 0101.

eth3: Digital DS21140 Tulip rev 34 at 0xdc00, EEPROM not present, =
00:00:D1:1E:7A:57, IRQ 10.





Not sure what is happening but it is definitely weird after win2k.  Also =
on bootup the bios shows the interfaces not all being on IRQ 10, like =
the de4x5 and tulip are showing.  They each have their own irq.  Any =
ideas anyone ?  I'm not passing any parameters to the board as well.  =
The board is an ECS p6ba-a+ with an award bios.



William


------=_NextPart_000_001B_01C18759.769945C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hello,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>&nbsp;&nbsp; Having a bit of a problem =
here.&nbsp;=20
The card was in the same slot, no configuration differences, probably =
the only=20
thing that changed was the IRQ's the interfaces were using.&nbsp; Before =
I was=20
goofing around with win2k, I had a successful installation of slackware =
with=20
2.4.16 kernel using the de4x5.o module for the DEC 21140, and I had 4 =
3c905c's=20
along with it (each running their own subnets).&nbsp; I installed win2k =
and it=20
ended up seeing it as an intel 21140 of course wasn't working, nothing =
was=20
working..... now when I go back to Linux, the card isn't working =
right.&nbsp;=20
Now either something was changed on the card itself, which I suspect, or =

something else is happening.&nbsp; When I insmod de4x5 this is what is =
in the=20
message console:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>eth0: DC21140 at 0xd000 (PCI bus 2, =
device 4), h/w=20
address 00:00:d1:1e:7a:54, and requires IRQ10 (provided by PCI=20
BIOS).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>de4x5.c:V0.546 2001/02/22 <A=20
href=3D"mailto:davies@maniac.ultranet.com">davies@maniac.ultranet.com</A>=
</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>eth1: DC21140 at 0xd000 (PCI bus 2, =
device 5), h/w=20
address 00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI=20
BIOS).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>de4x5.c:V0.546 2001/02/22 <A=20
href=3D"mailto:davies@maniac.ultranet.com">davies@maniac.ultranet.com</A>=
</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>eth2: DC21140 at 0xd000 (PCI bus 2, =
device 6), h/w=20
address 00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI=20
BIOS).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>de4x5.c:V0.546 2001/02/22 <A=20
href=3D"mailto:davies@maniac.ultranet.com">davies@maniac.ultranet.com</A>=
</FONT></DIV>
<DIV>
<DIV><FONT face=3DArial size=3D2>eth3: DC21140 at 0xd000 (PCI bus 2, =
device 7), h/w=20
address 00:00:d1:1e:7a:55, and requires IRQ10 (provided by PCI=20
BIOS).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>de4x5.c:V0.546 2001/02/22 <A=20
href=3D"mailto:davies@maniac.ultranet.com">davies@maniac.ultranet.com</A>=
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I can run dhcpcd on eth0 and get an ip =
and get out=20
onto the net just fine.&nbsp; If I do dhcpcd on either of the other =
interfaces I=20
get nothing.&nbsp; I can't figure out why the last 3 interfaces are =
getting the=20
same h/w address.&nbsp; It is baffling me.&nbsp; Maybe I"m missing =
something I=20
should have in the kernel, but I don't think so.&nbsp; Is there =
something I need=20
to write to the ANA-6944A/TX to get the eeprom back to where it should =
be.&nbsp;=20
When I use the tulip.o I each interface gets a different h/w address, =
but I=20
can't use dhcpcd to get ip's on the last 3 as well. Here is the tulip=20
information:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>
<P>Linux Tulip driver version 0.9.15-pre9 (Nov 6, 2001)</P>
<P>tulip0: EEPROM default media type Autosense.</P>
<P>tulip0: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)=20
block.</P>
<P>tulip0: MII transceiver #1 config 3100 status 7849 advertising =
0101.</P>
<P>tulip0: Advertising 01e1 on PHY 1, previously advertising 0101.</P>
<P>eth0: Digital DS21140 Tulip rev 34 at 0xd000, 00:00:D1:1E:7A:54, IRQ =
10.</P>
<P>tulip1: Controller 1 of multiport board.</P>
<P>tulip1: EEPROM default media type Autosense.</P>
<P>tulip1: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)=20
block.</P>
<P>tulip1: MII transceiver #1 config 3100 status 7849 advertising =
0101.</P>
<P>tulip1: Advertising 01e1 on PHY 1, previously advertising 0101.</P>
<P>eth1: Digital DS21140 Tulip rev 34 at 0xd400, EEPROM not present,=20
00:00:D1:1E:7A:55, IRQ 10.</P>
<P>tulip2: Controller 2 of multiport board.</P>
<P>tulip2: EEPROM default media type Autosense.</P>
<P>tulip2: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)=20
block.</P>
<P>tulip2: MII transceiver #1 config 3100 status 7849 advertising =
0101.</P>
<P>tulip2: Advertising 01e1 on PHY 1, previously advertising 0101.</P>
<P>eth2: Digital DS21140 Tulip rev 34 at 0xd800, EEPROM not present,=20
00:00:D1:1E:7A:56, IRQ 10.</P>
<P>tulip3: Controller 3 of multiport board.</P>
<P>tulip3: EEPROM default media type Autosense.</P>
<P>tulip3: Index #0 - Media MII (#11) described by a 21140 MII PHY (1)=20
block.</P>
<P>tulip3: MII transceiver #1 config 3100 status 7849 advertising =
0101.</P>
<P>tulip3: Advertising 01e1 on PHY 1, previously advertising 0101.</P>
<P>eth3: Digital DS21140 Tulip rev 34 at 0xdc00, EEPROM not present,=20
00:00:D1:1E:7A:57, IRQ 10.</P>
<P>&nbsp;</P>
<P><FONT face=3DArial></FONT>&nbsp;</P>
<P><FONT face=3DArial>Not sure what is happening but it is definitely =
weird after=20
win2k.&nbsp; Also on bootup the bios shows the interfaces not all being =
on IRQ=20
10, like the de4x5 and tulip are showing.&nbsp; They each have their own =

irq.&nbsp; Any ideas anyone ?&nbsp; I'm not passing any parameters to =
the board=20
as well.&nbsp; The board is an ECS p6ba-a+ with an award =
bios.</FONT></P>
<P><FONT face=3DArial></FONT>&nbsp;</P>
<P><FONT=20
face=3DArial>William</FONT></P></FONT></DIV></DIV></DIV></DIV></BODY></HT=
ML>

------=_NextPart_000_001B_01C18759.769945C0--