On Wednesday 14 November 2001 16:39, [EMAIL PROTECTED] wrote: > HELP! > > This is driving me absolutely positively mad. > > I have a Netgear F? 310TX network card, which is a PNIC 82c168 (tulip > clone). > > I *cannot* get this card to run reliably on the latest Debian stable > (2.2.Rev4). > > I have used both the tulip.o and the old_tulip.o drivers. > > The old_tulip.o module worked last night, but not this morning. In between > I installed some additional software, none of which had anything to do with > the kernel or kernel modules. > > I configure the driver with "options=13" which sets the card's mode to MII > 100BaseTx. This is what was working last night. When I ping my gateway > today, I get: > > eth0: Transmit error, Tx status 7fffc002. > eth0: The transmitter stopped! CSR5 is 206803a, CSR6 816ec002. > eth0: Transmit error, Tx status 7fffc000. > eth0: The transmitter stopped! CSR5 is 206801a, CSR6 816ec002. > eth0: Transmit error, Tx status 7fffc002. > eth0: The transmitter stopped! CSR5 is 206803a, CSR6 816ec002. > eth0: LC82C168 negotiated capability 00000000, CSR5 02660010. > eth0: LC82C168 MII PHY status ffff, Link partner report 0000, csr6 > 816ec000/816ee002. > > If I let the module autoprobe, I get > > eth0: Changing PNIC configuration to half-duplex, CSR6 01860000. > eth0: Changing PNIC configuration to half-duplex, CSR6 00420000. > eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. > eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. > eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. > eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. > eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. > eth0: Changing PNIC configuration to half-duplex, CSR6 00428000. > eth0: Changing PNIC configuration to half-duplex, CSR6 01868000. > ... > > This is a common network card. I've had absolutely no problems with these > cards with other Linux installations. > > Somebody who knows this driver, please help me. Thank you. > > > Arne Flones > flonesaw at longship dot net
hey bub...here's the lowdown on tulip drivers...you NEED to re-compile a nice new kernel. please. do it! :) you will not be sorry. i had the same trouble with the latest debian also. after a nice new re-compile of 2.4.14, which i included ALL the other drivers as modules, i actually found out that my card was indeed a tulip...BUT, it also 'shared' some code from another driver. here, take a look at my dmesg: Linux Tulip driver version 0.9.15-pre8 (Oct 11, 2001) eth0: ADMtek Comet rev 17 at 0xc8802c00, 00:20:78:10:C7:F1, IRQ 10. tulip1: MII transceiver #1 config 3000 status 7829 advertising 01e1. eth1: Lite-On 82c168 PNIC rev 32 at 0xc8804800, 00:A0:CC:52:B2:44, IRQ 12. PPP generic driver version 2.4.1 PPP Deflate Compression module registered you see that ADMTek thingy? well, i didn't get that until i made sure that in my kernel i enabled 'DMA off chip' booting and a workaround for my PCI buses. my tulip driver WOULD NOT WORK until i made a nice new kernel. again, i know this sounds nuts but i actually made ALL of the NIC card drivers into modules so i could test all of them! it's a little time consuming but it helped without a doubt! don't rely on the distro to make things nice for ya. learn more about the kernel!!! that's all there is to it! compile! compile! you won't be sorry you did it! TRUST ME! i was just as frustrated as you!!! GOOD LUCK! -jeff -- Q: How did you get into artificial intelligence? A: Seemed logical -- I didn't have any real intelligence.
