[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
tulip.c problems with 2.1.96+ versions
- From: Matti Aarnio <matti aarnio sonera fi>
- To: axp-list redhat com
- Cc: linux-net vger rutgers edu
- Subject: tulip.c problems with 2.1.96+ versions
- Date: Tue, 5 May 1998 02:13:37 +0300 (EEST)
Hello,
At my PWS433a Alpha machine I have two Tulip driven network
interfaces. One builtin 21142 "card", and one SMC 9332BDT(?)
card with 21140 chip. ("?" because its been awhile since I
looked at its labels...)
Everything works fine with kernel 2.1.92, but not so since
2.1.96 (I didn't try any of ..93 to ..95, so I don't know
when the change came).
Well, TRANSMIT does not work at 2.1.96 and latter, but
receive sure works. Running tcpdump does yield received
frames from the network.
If I install the module with option "debug=3", then I get
following status reports to dmesg once per second:
eth0: Transmit error, Tx status 7fffbc84.
eth0: Transmit error, Tx status 7fffbc84.
eth0: Transmit error, Tx status 7fffbc84.
eth0: Transmit error, Tx status 7fffbc84.
All of the base-address data et.al. appear to be same as
with 2.1.92, which works.
In this environment with PYXIS support, and new enough
MILO the system is compiled with these special CFLAGS:
-Wa,-m21164a -DBWX_USABLE -DBWIO_ENABLED
Compiling only the tulip.c without those flags does not
produce working driver. (I have not yet compiled entire
system without those flags to see if it affects anything.)
Modifying the driver to use the new pci_find_class() et.al.
revised PCI interface routines does not help either.
Nor using latter revisions of Becker et.al. Tulip driver.
/Matti Aarnio <matti.aarnio@sonera.fi>
<mea@nic.funet.fi>
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[]