From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 28 00:48:25 2007 Return-Path: X-Original-To: freebsd-mobile@freebsd.org Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43CD016A400 for ; Wed, 28 Mar 2007 00:48:25 +0000 (UTC) (envelope-from cstjean@cs.kent.edu) Received: from mscan1.cs.kent.edu (mscan1.cs.kent.edu [131.123.35.8]) by mx1.freebsd.org (Postfix) with ESMTP id F377913C4CC for ; Wed, 28 Mar 2007 00:48:24 +0000 (UTC) (envelope-from cstjean@cs.kent.edu) Received: from localhost (localhost.localdomain [127.0.0.1]) by mscan1.cs.kent.edu (8.12.11.20060308/8.12.10) with ESMTP id l2S0mNj3030972 for ; Tue, 27 Mar 2007 20:48:23 -0400 Received: from mscan1.cs.kent.edu ([127.0.0.1]) by localhost (mscan1.cs.kent.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30052-09 for ; Tue, 27 Mar 2007 20:48:19 -0400 (EDT) Received: from [192.168.1.100] (user-12l30r9.cable.mindspring.com [69.81.131.105]) (authenticated bits=0) by mscan1.cs.kent.edu (8.12.11.20060308/8.12.11) with ESMTP id l2S0mHso030963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 27 Mar 2007 20:48:19 -0400 Message-ID: <4609BB54.4050102@cs.kent.edu> Date: Tue, 27 Mar 2007 20:48:20 -0400 From: "Craig St. Jean" User-Agent: Thunderbird 1.5.0.10 (Windows/20070221) MIME-Version: 1.0 To: freebsd-mobile@freebsd.org References: 20070124.084635.1366907896.imp@bsdimp.com Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at cs.kent.edu Subject: cardbus not working X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2007 00:48:25 -0000 If your situation is like mine, find out which pci bus pci5 is on (probably pcib3). Assuming it was pcib3, you can see that your pcib3 is pci0:30:0 So try to change your subordinate value for that by experimenting with pciconf -wb pci0:30:0 0x1a VALUE. Again, if your situation is like mine, you will probably want to try 8 for VALUE (1 higher than your current) (so pciconf -wb pci0:30:0 0x1a 8) Good luck! Take a look at my issue that I've resolved for more in-depth information.