From owner-freebsd-mobile Fri Jan 30 22:26:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25993 for freebsd-mobile-outgoing; Fri, 30 Jan 1998 22:26:50 -0800 (PST) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from word.smith.net.au (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25946 for ; Fri, 30 Jan 1998 22:26:32 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id QAA00749; Sat, 31 Jan 1998 16:49:13 +1030 (CST) Message-Id: <199801310619.QAA00749@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Sean J. Schluntz" cc: "Goeringer, Michael" , freebsd-mobile@FreeBSD.ORG Subject: Re: Ach! Slot 0, unfielded interrupt 0 (unbreakable loop) In-reply-to: Your message of "Fri, 30 Jan 1998 14:13:26 -0800." <34D25085.39318F73@clicknet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 31 Jan 1998 16:49:12 +1030 From: Mike Smith Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe freebsd-mobile" > > For what it's worth, ep1 and ep0 have nothing to do with slot 0 and 1... > > I guess you could have two network cards in and then each would require > > thier own entry. In my example I make the printers poll and was using > > IRQ 7 for the card...is this what you did? > line when I get home :)> > > 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. 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. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\