From owner-freebsd-mobile Wed Feb 20 5:41:44 2002 Delivered-To: freebsd-mobile@freebsd.org Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by hub.freebsd.org (Postfix) with ESMTP id 4A40C37B402 for ; Wed, 20 Feb 2002 05:41:40 -0800 (PST) Received: (from david@localhost) by bunrab.catwhisker.org (8.11.6/8.11.6) id g1KDfem68660 for freebsd-mobile@FreeBSD.ORG; Wed, 20 Feb 2002 05:41:40 -0800 (PST) (envelope-from david) Date: Wed, 20 Feb 2002 05:41:40 -0800 (PST) From: David Wolfskill Message-Id: <200202201341.g1KDfem68660@bunrab.catwhisker.org> Subject: Re: why would my laptop suddenly start failing to probe pccards? Cc: freebsd-mobile@FreeBSD.ORG In-Reply-To: <20020220074503.A21424@blackhelicopters.org> Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Date: Wed, 20 Feb 2002 07:45:03 -0500 >From: Michael Lucas >I've seen this before. >The solution was an utterly cold shutdown between Win & FreeBSD. Shut >off the power, completely; not standby mode, not suspend, not booting, >not sitting at the BIOS screen, cold shutdown. Go get a cup of >coffee. Sip your coffee and hit the power button. >Win will occasionally leave the PC Cards in a slightly scrambled >state. >IIRC, this has come up before... should it be a FAQ? Well, what struck me by surprise is when a very similar thing happened on my laptop, which only runs FreeBSD.... In my case, it happened when I set up my normal -CURRENT slice to run a kernel based on NEWCARD, then tried a reboot back to -STABLE (different slice of the disk). I found that power-cycling the card itself (whether via pccardc or eject/insert) didn't do the job, but power-cycling the laptop itself seems to be sufficient (and, evidently, necessary). The card in question is a Cisco 340 Series 802.11b NIC. (I tried an Intel CE3 (xe driver, under -STABLE), but my -CURRENT kernel didn't seem to recognize it. I'll see about looking into this in more detail today.) I thought the behavior odd when I noticed it first 2 days ago; yesterday, after building that day's -CURRENT, it happened again. I rather expect it to happen today, after I build today's -CURRENT.... Anyhow, seeing the behavior in question occur with a switch between OSs for which the sources are available may provide enough additional information to better understand the mechanism in question. Cheers, david (links to my resume at http://www.catwhisker.org/~david) -- David H. Wolfskill david@catwhisker.org I believe it would be irresponsible (and thus, unethical) for me to advise, recommend, or support the use of any product that is or depends on any Microsoft product for any purpose other than personal amusement. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message