Re: Abysmal RECV network performance

Hi, I'm guessing that the tulip driver is not setting the chip up correctly. I've seen this happen with other tulip variants (21143) when tries to autonegotiate. if you do an ifconfig eth1 you will see numerous carrier and crc errors. Set the tulip_debug flag to 2 or 3 in /etc/modules.conf and

Re: Abysmal RECV network performance

Hi, I'm guessing that the tulip driver is not setting the chip up correctly. I've seen this happen with other tulip variants (21143) when tries to autonegotiate. if you do an ifconfig eth1 you will see numerous carrier and crc errors. Set the tulip_debug flag to 2 or 3 in /etc/modules.conf and

Re: magic device renumbering was -- Re: Linux 2.4.2ac20

Hi, The solution is not to go down the path2inst road, that is full of its own traps. You want volume labels via a volume manager (do lvm and raid already do this?) and/or filesystem labels (see e2fslabel). This won't solve all of the ills associated with device instance changes, but it will

Re: magic device renumbering was -- Re: Linux 2.4.2ac20

Hi, The solution is not to go down the path2inst road, that is full of its own traps. You want volume labels via a volume manager (do lvm and raid already do this?) and/or filesystem labels (see e2fslabel). This won't solve all of the ills associated with device instance changes, but it will

Re: ARP out the wrong interface

Hi, What you describe below is having the client mis-addressed to have the same IP as the server. Is this what you meant? skd On Thu, Feb 08, 2001 at 09:09:49PM -0800, dean gaudet wrote: > this appears to occur with both 2.2.16 and 2.4.1. > > server: > > eth0 is 192.168.250.11 netmask

Re: ARP out the wrong interface

Hi, What you describe below is having the client mis-addressed to have the same IP as the server. Is this what you meant? skd On Thu, Feb 08, 2001 at 09:09:49PM -0800, dean gaudet wrote: this appears to occur with both 2.2.16 and 2.4.1. server: eth0 is 192.168.250.11 netmask

tulip autonegotiation patch

Hi, This one-liner fixes a subtle 21143 autonegotiation problem for me on a Zynx quad card. The driver would claim to negotiate 100-FD, but would report late collisions and bad transmit throughput. The driver still allows packets to be transmitted during autonegotiation, but that only drops a

tulip autonegotiation patch

Hi, This one-liner fixes a subtle 21143 autonegotiation problem for me on a Zynx quad card. The driver would claim to negotiate 100-FD, but would report late collisions and bad transmit throughput. The driver still allows packets to be transmitted during autonegotiation, but that only drops a