Date: Sun, 26 Jan 2003 16:51:55 +0800 From: Greg Lehey <grog@freebsd.org> To: Kevin Oberman <oberman@es.net> Cc: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>, "M. Warner Losh" <imp@bsdimp.com>, mobile@freebsd.org Subject: Re: How to make an Intel EtherExpress known to xe(4)? Message-ID: <20030126085155.GD1982@sydney.worldwide.lemis.com> In-Reply-To: <20030125230756.BC4195D06@ptavv.es.net> References: <20030125235520.A97813@uriah.heep.sax.de> <20030125230756.BC4195D06@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 25 January 2003 at 15:07:56 -0800, Kevin Oberman wrote: >> Date: Sat, 25 Jan 2003 23:55:20 +0100 >> From: Joerg Wunsch <j@uriah.heep.sax.de> >> Sender: owner-freebsd-mobile@FreeBSD.ORG >> >> As M. Warner Losh wrote: >> >>> : In addition to make it known to the files in /sys/dev/xe/, >>> : what else needs to be done to handle this card? >>> >>> Index: if_xe_pccard.c >> ... >>> Should be all that's needed, unless it has a modem built-in. >> >> Yep, thanks, it is all to make it known: >> >> xe0: <Intel EtherExpress PRO/100> at port 0x100-0x10f irq 11 function 0 config 1 on pccard0 >> xe0: Intel CE3, bonding version 0x45, 100Mbps capable >> xe0: DingoID = 0x444b, RevisionID = 0x1, VendorID = 0 >> xe0: Ethernet address 00:a0:c9:bc:b5:ef >> >> However, when trying to use it i get: >> >> xe0: discard oversize frame (ether type 800 flags 3 len 1518 > max 1514) >> >> This didn't happen with that card under 4.x. I might look >> into the differences... The connection is not usable that >> way, it seems all packets are thrown away as being oversized. >> >> Maybe as a workaround just assume it's a full-sized packet, >> and only discard the `oversized' bytes? If this was in >> error, the higher protocol layers will throw the packet >> away anyway. > > This is typical of receiving 802.1q tagged frames, but I have been > getting this error on my current system with a Xircom RE-100 card and > I am reasonably sure that i am not getting any tagged frames where > it's located. I suspect a bug in the driver, but have not had time to > look at it to this point. (Like, maybe, it is counting the FCS bytes > as part of the frame, which would make a full sized frame 1500 bytes > of data plus 6 bytes source, 6 bytes destination, 2 bytes of protocol > information, and 4 bytes of FCS for a total of (1500+6+6+2+4=1518). Yes, I reported a similar problem with a Xircom card (the thick red one with the RJ-45 connector, if that's enough to identify it; sorry, I don't have net connectivity at the moment) a while back. I've confirmed that the packets leave the source with length 1514 and at the destination with reported 1518 bytes. That doesn't happen when the receiving end is running release 4. > This is only conjecture until someone looks at the driver. Indeed. I don't see me having time in the near future. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030126085155.GD1982>