tulip driver still broken
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
It seems that the driver incorrectly configures the card for full duplex mode and I could not figure out how to override this with the new MODULE_PARM macro.
I am now using the stable driver 0.9.14 from sourceforge.net which works fine.
Further information available by request!
Tom
Quantum Mechanics is God's version of "Trust me."
Signature · 3 lines
T h o m a s Z e h e t b a u e r ( TZ251 )
PGP encrypted mail preferred - KeyID 96FFCB89
mail [email protected]I am afraid of post these days. However, I must comment that I too am having trouble with the tulip driver, on several SMC nic's that use the DEC chipset. I tried mii_tool, with no success.
I have just been copying the tulip driver from 2.4.4 forward... because I
don't have enough time to try and create an intelligent error report.
thanks,
joshua
Quoted 16 lines · Thomas Zehetbauer
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
It seems that the driver incorrectly configures the card for full duplex mode and I could not figure out how to override this with the new
MODULE_PARMmacro.I am now using the stable driver 0.9.14 from sourceforge.net which works fine.
Further information available by request!
Tom
Quantum Mechanics is God's version of "Trust me."
Quoted 6 lines · Joshua Schmidlkofer
I am afraid of post these days. However, I must comment that I too am having trouble with the tulip driver, on several SMC nic's that use the DEC chipset. I tried
mii_tool, with no success.I have just been copying the tulip driver from 2.4.4 forward... because I
don't have enough time to try and create an intelligent error report.
Thanks for the report!
Currently there are problems with 21041 old chipsets, which include SMC and several other cards. You can use 0.9.14 from
http://sf.net/projects/tulip/ until I get around to fixing it.
(off vacation, but now moving to new house w/ no Internet :))
Jeff
Quoted 11 lines · Thomas Zehetbauer
Quoted 10 lines
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
It seems that the driver incorrectly configures the card for full duplex mode and I could not figure out how to override this with the new
MODULE_PARMmacro.I am now using the stable driver 0.9.14 from sourceforge.net which works fine.
Quoted 6 lines · Jeff Garzik
Quoted 4 lines · Joshua Schmidlkofer
I am afraid of post these days. However, I must comment that I too am having trouble with the tulip driver, on several SMC nic's that use the DEC chipset. I tried
mii_tool, with no success.
Quoted 8 lines
Quoted 2 lines
I have just been copying the tulip driver from 2.4.4 forward... because I
don't have enough time to try and create an intelligent error report.Thanks for the report!
Currently there are problems with 21041 old chipsets, which include SMC and several other cards. You can use 0.9.14 from
http://sf.net/projects/tulip/ until I get around to fixing it.
My 21041 is also not working with late 2.4 series tulip drver. I've heard the de4x5 driver does however work.
Signature · 5 lines
Patrick Cole - Debian Developer <[email protected]> - Linux.com Volunteer <[email protected]> - ANU JCSMR ICU Staff <[email protected]> - PGP 1024R/60D74C7D C8 E0 BC 79 69 BE 78 99 AA 0F EB 16 F8 4B FE 5A
Quoted 5 lines · Jeff Garzik
Quoted 4 lines · Joshua Schmidlkofer
I am afraid of post these days. However, I must comment that I too am having trouble with the tulip driver, on several SMC nic's that use the DEC chipset. I tried
mii_tool, with no success.
Quoted 7 lines
Quoted 2 lines
I have just been copying the tulip driver from 2.4.4 forward... because I
don't have enough time to try and create an intelligent error report.Thanks for the report!
Currently there are problems with 21041 old chipsets, which include SMC and several other cards.
Hm, I reported few times problems with DS21143 Tulip rev 65, which is not exactly old, and with anything above tulip-0.9.14, and did not get back even a half line acknowledment not mentioning annoucements of fixes. I also posted mii-diag output from a card in working and not working state.
I have to admit, though, that I did not test that really recently. RSN...
Michal
Quoted 4 lines · Thomas Zehetbauer
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
How is the sourceforge driver different than the one at www.scyld.com?
Signature · 4 lines
Chris Friesen | MailStop: 043/33/F10 Nortel Networks | work: (613) 765-0557 3500 Carling Avenue | fax: (613) 765-2986 Nepean, ON K2H 8E9 Canada | email: [email protected]
Quoted 7 lines · Chris Friesen
Quoted 4 lines · Thomas Zehetbauer
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
How is the sourceforge driver different than the one at www.scyld.com?
They are totally different, though they have a common origin.
Jeff
Quoted 9 lines · Chris Friesen
Quoted 4 lines · Thomas Zehetbauer
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
How is the sourceforge driver different than the one at www.scyld.com?
Becker (Scyld) has only recently gotten his drivers to even compile on 2.4 kernel, and they are still beta quality for 2.4, evidently.
There seem to be attempts to keep the drivers in sync, functionally, but the architectures have diverged quite a lot...
Ben
Signature · 3 lines
Ben Greear <[email protected]> <[email protected]> President of Candela Technologies Inc http://www.candelatech.com ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
Quoted 18 lines · Ben Greear
Quoted 9 lines · Chris Friesen
Quoted 4 lines · Thomas Zehetbauer
My genuine digital network interface card ceased to work with the tulip driver contained in kernel revisions >= 2.4.4 and the development driver from sourceforge.net.
How is the sourceforge driver different than the one at www.scyld.com?
Becker (Scyld) has only recently gotten his drivers to even compile on 2.4 kernel, and they are still beta quality for 2.4, evidently.
There seem to be attempts to keep the drivers in sync, functionally, but the architectures have diverged quite a lot...
Quoted 6 lines
Ben
--
Ben Greear <[email protected]> <[email protected]>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
Hi,
I am currently using a Xircom Ethernet adapter (tulip_cb module) with a 2.4.5 kernel.
The only way I have found to make it work is to turn on promiscuous mode (with 'tcpdump -i eth0 -n > /dev/null') after bootup. I can turn it off after a few minutes without problem.
I don't know if tulip driver I am using has been patched since I haven't compiled this 2.4.5 kernel myself. Here is driver bootup information:
tulip.c:v0.91g-ppc 7/16/99 [email protected] (modified by [email protected] for XIRCOM CBE, fixed by Doug Ledford)
eth0: Xircom Cardbus Adapter (DEC 21143 compatible mode) rev 3 at 0x200, 00:10:A4:C0:2A:30, IRQ 9.
eth0: MII transceiver #0 config 3100 status 7809 advertising 01e1.
Hope this helps
Regards
--
Joseph Bueno
Quoted 6 lines · On Wed, 1 Aug 2001 [email protected] wrote:
I am currently using a Xircom Ethernet adapter (
tulip_cbmodule) with a 2.4.5 kernel.The only way I have found to make it work is to turn on promiscuous mode (with 'tcpdump -i eth0 -n >
/dev/null') after bootup. I can turn it off after a few minutes without problem.
i saw something like that with a wireless ethernet card, but presumed it to be something wrong with WAP+multicast, plus it doesn't happen with new card firmware.
at any rate, this made my card work, and sounds like it would be better than running tcpdump and killing it after a few minutes. the critical element in getting things working was getting traffic while the interface was in promisc mode (arp replies to wrong mac address maybe?)
ifconfig ethX promisc
ping -n -c 5 <pick a remote ip>
ifconfig ethX -promisc
if you have no traffic for a few minutes, it might break again.
justin
Quoted 10 lines · Justin Guyett
Quoted 6 lines · On Wed, 1 Aug 2001 [email protected] wrote:
I am currently using a Xircom Ethernet adapter (
tulip_cbmodule) with a 2.4.5 kernel.The only way I have found to make it work is to turn on promiscuous mode (with 'tcpdump -i eth0 -n >
/dev/null') after bootup. I can turn it off after a few minutes without problem.
Quoted 9 lines
i saw something like that with a wireless ethernet card, but presumed it to be something wrong with WAP+multicast, plus it doesn't happen with new card firmware.
at any rate, this made my card work, and sounds like it would be better than running tcpdump and killing it after a few minutes. the critical element in getting things working was getting traffic while the interface was in promisc mode (arp replies to wrong mac address maybe?)
That's right.
In fact, I generally start a ping to a remote IP address after bootup and, if I don't get any response (which is always the case), I start tcpdump and I do some network activity before stopping it.
Quoted 3 lines
ifconfig ethX promisc
ping -n -c 5 <pick a remote ip>
ifconfig ethX -promisc
In fact, I ran tcpdump to check what was going on and, since it "solved" the problem, I didn't check for a better way to do it. Obviously, your solution is better.
Quoted 2 lines
if you have no traffic for a few minutes, it might break again.
Hopefully, there is some periodic network activity on my machine (at least checking of my POP account), so it doesn't break.
Quoted 2 lines
justin
Thanks
--
Joseph Bueno
NetClub/Trader.com
Quoted 6 lines · On Wed, 1 Aug 2001 [email protected] wrote:
I am currently using a Xircom Ethernet adapter (
tulip_cbmodule) with a 2.4.5 kernel.The only way I have found to make it work is to turn on promiscuous mode (with 'tcpdump -i eth0 -n >
/dev/null') after bootup. I can turn it off after a few minutes without problem.
To fix this problem, either use the xircom_tulip_cb driver in 2.4.x, or use the recently updated tulip_cb driver that comes with the pcmcia_cs package.