From owner-freebsd-mobile  Fri Jan 30 22:51:11 1998
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id WAA29742
          for freebsd-mobile-outgoing; Fri, 30 Jan 1998 22:51:11 -0800 (PST)
          (envelope-from owner-freebsd-mobile@FreeBSD.ORG)
Received: from dns.pinpt.com (dns.pinpt.com [205.179.195.1])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29737
          for <freebsd-mobile@FreeBSD.ORG>; Fri, 30 Jan 1998 22:51:10 -0800 (PST)
          (envelope-from schluntz@clicknet.com)
Received: from clicknet.com (gatemaster.pinpt.com [205.179.195.65])
	by dns.pinpt.com (8.8.7/8.8.7) with ESMTP id WAA02871;
	Fri, 30 Jan 1998 22:43:42 -0800 (PST)
Message-ID: <34D2C942.BB402679@clicknet.com>
Date: Fri, 30 Jan 1998 22:48:34 -0800
From: "Sean J. Schluntz" <schluntz@clicknet.com>
Organization: PinPoint Software Corporation
X-Mailer: Mozilla 4.02 [en]C-DIAL  (WinNT; U)
MIME-Version: 1.0
To: Mike Smith <mike@smith.net.au>
CC: "Goeringer, Michael" <goeringerm@keywest.ird.rl.af.mil>,
        freebsd-mobile@FreeBSD.ORG
Subject: Re: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop)
References: <199801310619.QAA00749@word.smith.net.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org
X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-mobile"

> > No, I've got it setup for 0x300 and irq 10, I've set those up in the
> > 3Com utility and have verified that NT sees it that way as well. My
> > orriginal problem as an unable to allocate driver.
> 
> Note that the port and IRQ values in the CIS tuples are purely
> advisory; they don't affect the operation of the card in any way.

You mean in the kernel definition or in pccard.conf.  Unfortunately I'm
not sure what 'CIS tuples' is.


> The "driver allocation failed" message means that the 'ep' driver,
> given the mappings supplied, failed to locate your card.
> 
> This may mean that the port range you have specified is actually
> occupied by other hardware, or that your card is not behaving in a
> fashion that the 'ep' driver can handle.
> 
> You should add some debugging messages to the 'ep' driver's probe
> routines to determine the cause of the rejection.

Hm, unfortunately this is a step beyond me.  I can give it a shot, but
I'm pretty basic when it comes to coding C.

-Sean