From owner-freebsd-mobile Sat Jan 31 22:33:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25996 for freebsd-mobile-outgoing; Sat, 31 Jan 1998 22:33:16 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25991 for ; Sat, 31 Jan 1998 22:33:14 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id XAA04188; Sat, 31 Jan 1998 23:33:00 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id XAA23544; Sat, 31 Jan 1998 23:32:58 -0700 Date: Sat, 31 Jan 1998 23:32:58 -0700 Message-Id: <199802010632.XAA23544@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: "Sean J. Schluntz" , "Sean J. Schluntz" , "Goeringer, Michael" , freebsd-mobile@FreeBSD.ORG Subject: Re: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop) In-Reply-To: <199802010119.LAA02375@word.smith.net.au> References: <199802010052.QAA14335@gromit.pinpt.com> <199802010119.LAA02375@word.smith.net.au> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-mobile" > > >Make sure pccardd is *NOT* running. Insert the card and say > > >"pccardc dumpcis". Look through the output for an entry like this: > > > > Does killing it after it launches ok? I found that I got strange errors > > if I turned off pccard in rc.conf but was able to get the info you > > mentioned when I let the system load it on boot and then killed it. > > The fact that things don't work unless you have run pccardd are > strange; it certainly *should* work. No, this is expected behavior since there isn't any memory window (??) allocated in the kernel yet. If I had a working laptop I could tell you more, but mine is down for the count (hard-disk failure), and work wants to replace it. But, they aren't willing to replace it for about 4-5 months, and they aren't willing to buy me a hard-drive for this ancient (but working) box. Nate