From owner-freebsd-current Mon Jan 20 5:31: 0 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A3A737B401 for ; Mon, 20 Jan 2003 05:30:59 -0800 (PST) Received: from server.merchantsbarter.com (server.merchantsbarter.com [198.78.66.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8819D43F13 for ; Mon, 20 Jan 2003 05:30:58 -0800 (PST) (envelope-from damien@tougas.net) Received: from [192.168.1.105] (me-lewiston-pw-835.mint.adelphia.net [216.227.167.76]) by server.merchantsbarter.com (Postfix) with ESMTP id 6B387D49 for ; Mon, 20 Jan 2003 05:30:52 -0800 (PST) Date: Mon, 20 Jan 2003 08:39:20 -0500 From: Damien Tougas To: freebsd-current@freebsd.org Subject: Problems with FreeBSD-5.0 and comms/ltmdm Message-ID: <129320000.1043069960@buddy.tougas.net> X-Mailer: Mulberry/2.2.1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; FORMAT=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, I am running FreeBSD 5.0-RELEASE on my laptop and just tried installing the comms/ltmdm port for my Lucent Winmodem. The port builds and installs without any problems, and when I reboot, the kernel module loads and detects the modem. However, if I try to initiate any kind of network activity (i.e. ping another machine) over my ethernet interface (a 3COM pcmcia ethernet card using the ep driver), the OS locks up instantly. There are no panics, error messages, or anything, all I can do is hard boot. As soon as I uninstall the port, the problem goes away. Any suggestions? Is there more information I can give that would be helpful to solving this problem? Please respond to me directly, as I am not subscribed to this list. Thank you. -- Damien Tougas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message