From owner-freebsd-questions@FreeBSD.ORG Sun Jan 18 03:50:40 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E535516A4CE for ; Sun, 18 Jan 2004 03:50:40 -0800 (PST) Received: from mail.pinboard.com (mail.pinboard.com [194.209.195.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96CF643D41 for ; Sun, 18 Jan 2004 03:50:37 -0800 (PST) (envelope-from kurt@pinboard.com) Received: (from uucp@localhost)UUCP id MAA82930 for freebsd-questions@freebsd.org; Sun, 18 Jan 2004 12:50:36 +0100 (CET) (envelope-from kurt@pinboard.com (kurt@pinboard.com)) (client-IP ) Received: (from kurt@localhost) (8.9.3p2-20030920/8.9.3/20011223-00-KK) id MAA61305; Sun, 18 Jan 2004 12:03:39 +0100 (CET) (envelope-from kurt (kurt)) (client-IP ) Date: Sun, 18 Jan 2004 12:03:38 +0100 From: pbdlists@pinboard.com To: freebsd-questions@freebsd.org Message-ID: <20040118120338.A59685@pinboard.com> Mail-Followup-To: pbdlists@pinboard.com, freebsd-questions@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: ep driver problem in 5.2? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2004 11:50:41 -0000 Today I installed FBSD 5.2 on my main notebook because I want to make the switch from 4.7. I have a 3Com Megahertz 10/100 LAN PC Card Model 3CCFE574BT. ep0: <3Com Megahertz 574B> at port 0x100-0x11f irq 11 function 0 config 1 on pccard0 Unknown ID: 0x201 ep0: Ethernet address 00:50:da:d3:6b:22 The default kernel is being used, no changes made. This card was working flawlessly all the time with FBSD 4.5/4.7, did autonegotiation perfectly, no problem at all, not even plugging the cable out on my 100 Mb switch and plugging it in on a 10 Mb hub or vice versa. With 5.2, however, the card works fine right right after ifconfig ep0 up, but: - it stops working if there has not been any traffic through the card for a while (have not yet been able to determine the exact time) - if there is traffic through the card all the time (eg pinging another host continuously) it does not stop working - broadcasts, arp requests and other packets going to all nodes on the network seem to do the trick as well as a constant ping - the autonegotiating switch, to which it is connected, still shows the card is there and in 100 MB full duplex mode - ifconfig ep0 down followed by ifconfig ep0 up brings the card back to life again - if connecting the card to a 10 MB hub, there are no problems, it continues to work properly, even if there is no traffic through it for some time Unfortunately the ep driver does not support setting the media, otherwise it might be possible to work around the problem. At the moment I'm at a loss, not knowing how to get this to work. Writing a startup script which does not return and pings another host on the network all the time is not quite the solution I'd be happy to implement... Kurt