From owner-freebsd-mobile@FreeBSD.ORG Fri Jun 13 12:16:56 2003 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7B31B37B404 for ; Fri, 13 Jun 2003 12:16:56 -0700 (PDT) Received: from mail.speakeasy.net (mail13.speakeasy.net [216.254.0.213]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7976043FA3 for ; Fri, 13 Jun 2003 12:16:55 -0700 (PDT) (envelope-from aron@slam.cc) Received: (qmail 21842 invoked from network); 13 Jun 2003 19:16:54 -0000 Received: from unknown (HELO slam.cc) ([216.254.102.98]) (envelope-sender ) by mail13.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 13 Jun 2003 19:16:54 -0000 Date: Fri, 13 Jun 2003 15:16:53 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: "Kevin Oberman" From: Aron Roberts In-Reply-To: <20030613190028.8AAD95D04@ptavv.es.net> Message-Id: <9788B000-9DD3-11D7-967B-000502916C37@slam.cc> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: freebsd-mobile@freebsd.org Subject: Re: mwavem on 5.1-REL panic X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 19:16:56 -0000 Thanks for the update :) I had a feeling this might be the case. Thanks for having it work on 4.x etc.. :) On Friday, June 13, 2003, at 03:00 PM, Kevin Oberman wrote: >> Date: Fri, 13 Jun 2003 14:43:50 -0400 >> From: Aron Roberts >> Sender: owner-freebsd-mobile@freebsd.org >> >> I am having a problem with the mwavem in 5.1-RELEASE which causes the >> kernel to panic immediately after the module is loaded. Is anyone else >> experiencing this problem? >> >> I am using a thinkpad 600X. >> >> The only thing out of the ordinary that I did was remove the mknod >> command from the port makefile.. since as near as I can tell the fancy >> new devfs means I don't have to do that any more. >> >> Is this just an issue of the port needing to be updated to work with >> 5.1? or are others not having this problem? > > Aron, > > Sorry. I need to mark that one a BROKEN on versions > 5 until I can > get it updated. > > It does not understand devfs at the moment, so it has no chance of > working with 5.1. As we speak I am updating my 600E to 5.1 to take a > shot at fixing it, but I am not a simply turned Simon Walton's work on > this into a port, so I don't make any promises as to when or if I'll > get it fixed. > -- > R. Kevin Oberman, Network Engineer > Energy Sciences Network (ESnet) > Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) > E-mail: oberman@es.net Phone: +1 510 486-8634