'Me too' on the transmit timeout, also need 1.05 driver

[Robert von Bismarck]

Switches do make a difference. We use cisco Catalyst 2924XL here, and we get
the infamous "Transmit timed out.." messages as well.. we did not have those
on the Catalyst 19xx series, but of course those are 10B-T switches...
We tried the same board on a 3Com SuperStackII switch, and it works
flawlessly, we could not keep the switch though...


--
Robert von Bismarck
Network Systems Engineer
Petrel Communications SA / SPAN
Tel : +41 22 304 47 47
Fax : +41 22 300 48 43
WWW : http://www.petrel.ch
e-mail : rvb@petrel.ch

> -----Original Message-----
> From:	Andreas Vierengel [SMTP:andreas@Vierengel.de]
> Sent:	jeudi, 7. octobre 1999 08:40
> To:	Simon Andrew Boggis
> Cc:	linux-eepro100@cesdis1.gsfc.nasa.gov
> Subject:	Re: 'Me too' on the transmit timeout, also need 1.05 driver
> 
> 
> > Incidently, we use 3com 3300 switches and NuSwitch (now Extreme
> Networks, I
> > believe), as it seems from some of the recent discussion that certain
> switches
> > *may* a factor in some problems.
> 
> They ARE. Even FD or HD influences the whole thing. Our networkprovider
> uses
> SMC-Switches (don't know the exact model, because I've never seen it ...),
> but I
> did get the infamous "transmit timed out..."-error after v1.05. Also
> versions
> after 0.99B generated up to 50% collisions in FD on an 3Com 100MBit
> office-hub,
> on which there were only 2 connected machines. Both Linux 2.0.36 with
> eepro100
> ...
> 
> My current configuration works in 100MBit, FD (NIC attached to a Switch)
> and
> v1.05 ...
> 
> I didn't manage to reproduce it in different environement (brand of
> switch, HD
> or FD, 10 or 100MBit, load factor).
> 
> Sadly...
> 
> --Andy