Re: Re: smc1244TX

> What driver version are you using?
> What is the detection message (shown when booting)?

I have used some driver versions:

Linux-2.4.22:

	Linux Tulip driver version 0.9.15-pre12 (Aug 9, 2002)
	PCI: Found IRQ 11 for device 00:0a.0
	eth0: ADMtek Comet rev 17 at 0xd8ae9000, 0B:00:0B:00:0B:00, IRQ 11.

Last drivers from web:

	pci-scan.c:v1.11 8/31/2002  Donald Becker <[email protected]> http://www.scyld.com/linux/drivers.html
	tulip.c:v0.97 7/22/2003  Written by Donald Becker <[email protected]>	 http://www.scyld.com/network/tulip.html
	eth0: ADMtek Centaur-P rev 17 at 0xd9c4d000, 0B:00:0B:00:0B:00, IRQ 11.
	eth0:  MII transceiver #1 config 3100 status 786d advertising 05e1

Linux 2.6-test5:

	Linux Tulip driver version 1.1.13 (May 11, 2002)
	eth0: ADMtek Comet rev 17 at 0xd8937000, 0B:00:0B:00:0B:00, IRQ 10

As you see, ever have same result.

> I'm guessing that you have a lot
> of error reports in the logs.

	In logs i have no errors ( dmesg ) but in stats for eth0 yes. a lot.
 
> You have an IRQ problem.

I have no reports for an irq problem.

thanks.

Uxio.



El Jueves, 11 de Septiembre de 2003 15:59, Donald Becker escribió:
> On Thu, 11 Sep 2003, Uxio Faria wrote:
> > I have the SMC1244TX board:
> >
> > # lspci
> > 00:0d.0 Ethernet controller: Linksys Network Everywhere Fast Ethernet
> > 10/100 model NC100 (rev 11) #lspci -n
> > ...
> > 00:0d.0 Class 0200: 1317:0985 (rev 11)
> > ...
>
> Just the info we need... thanks.
>
> > OK the diag tool shows this:
> >
> > # ./tdiag -aaem
> > tulip-diag.c:v2.17 5/6/2003 Donald Becker ([email protected])
> >  http://www.scyld.com/diag/index.html
> > Index #1: Found a ADMtek AL985 Centaur-P adapter at 0xec00.
>
> ...
>
> >  Transmit stopped, Receive stopped.
> >   The Rx process state is 'Waiting for packets'.
> >   The Tx process state is 'Stopped'.
> >   The transmit threshold is 128.
> >  Interrupt sources are pending!  CSR5 is fc06c812.
> >    Tx complete indication.
> >    Link passed indication.
> >    Timer expired indication.
> >    Early Rx indication.
>
> You have an IRQ problem.
>
> > The problem i have is that board not transmits well. Pings and short
> > udp packets ( like dns lookups ) works well but TCP not.
>
> The pings are only "working" because the card receives a few packets
> when trying to recover from the error.  I'm guessing that you have a lot
> of error reports in the logs.
>
> > OK. the first thing that is "rare" is the MAC address that ifconfig
> > shows on screen, which is not correct as in diag tool.
>
> What driver version are you using?
> What is the detection message (shown when booting)?
>
> > I suppose that this board is a little different to similar others.
>
> Not likely: there is only one way to put a Comet chip on a board.

_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip