From owner-freebsd-current@FreeBSD.ORG Thu Apr 10 00:05:00 2003 Return-Path: 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 4912037B401; Thu, 10 Apr 2003 00:05:00 -0700 (PDT) Received: from ns3.safety.net (ns3.safety.net [216.40.201.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id A789143FB1; Thu, 10 Apr 2003 00:04:59 -0700 (PDT) (envelope-from cbiffle@safety.net) Received: from localhost (rs.rackshack.net.safety.net [216.40.201.32]) by ns3.safety.net (8.10.2/8.10.2) with ESMTP id h3A74vA20790; Thu, 10 Apr 2003 00:04:58 -0700 From: "Cliff L. Biffle" To: Mark Sergeant , mobile@freebsd.org Date: Thu, 10 Apr 2003 00:05:46 -0700 User-Agent: KMail/1.5 References: <1049890166.1077.4.camel@xyzzy.wireless.snsonline.net> In-Reply-To: <1049890166.1077.4.camel@xyzzy.wireless.snsonline.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200304100005.46900.cbiffle@safety.net> cc: current@freebsd.org Subject: Possible issue with wi (Was:Problem with Toshiba Wirless Lan card after latest cvsup) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Apr 2003 07:05:00 -0000 On Wednesday 09 April 2003 05:09 am, Mark Sergeant wrote: > After a cvsup 8 hours ago and subsequent build world I've found a slight > problem, I no longer have a working wireless card. I'm cvsupping again > in the hope that this will fix the problem but in the meantime I get the > following on boot... I can reproduce the issue with exactly the same symptoms. I supped the day before yesterday and my build completed yesterday (slow notebook). However, my card didn't stop being recognized until several hours -after- I had booted the new system. I've been through several kernel rebuilds today in an attempt to fix it. The CIS info reported when the debugging sysctls are set is absolutely correct, and maps to info in pccarddevs. The driver is simply not noticing the card, but -- here's the kicker -- most other cards work. It seems to be an issue with wi. Anyone else getting this? I'm supping and rebuilding in the hope of a fix. -Cliff L. Biffle