Date: Fri, 30 Jan 1998 22:48:34 -0800 From: "Sean J. Schluntz" <schluntz@clicknet.com> 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) Message-ID: <34D2C942.BB402679@clicknet.com> References: <199801310619.QAA00749@word.smith.net.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34D2C942.BB402679>