From owner-freebsd-current@FreeBSD.ORG  Tue Mar  2 18:30:15 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 8209016A4CE; Tue,  2 Mar 2004 18:30:15 -0800 (PST)
Received: from fe5.cox-internet.com (fe5-cox.cox-internet.com [66.76.2.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 007C443D1F; Tue,  2 Mar 2004 18:30:15 -0800 (PST)
	(envelope-from muntyan@tamu.edu)
Received: from mlap ([66.233.123.200]) by fe5.cox-internet.com
	ac98e04b23802b25ff26d48c352bda07)
	with ESMTP id <20040303023013.ERSS377.fe5@mlap>;
	Tue, 2 Mar 2004 20:30:13 -0600
From: Yevgen Muntyan <muntyan@tamu.edu>
To: John Baldwin <jhb@FreeBSD.org>
Date: Tue, 2 Mar 2004 20:30:09 -0600
User-Agent: KMail/1.6
References: <200402291903.20499.muntyan@tamu.edu>
	<200403011916.17683.muntyan@tamu.edu> <200403021147.50480.jhb@FreeBSD.org>
In-Reply-To: <200403021147.50480.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="windows-1251"
Content-Transfer-Encoding: 7bit
Message-Id: <200403022030.09432.muntyan@tamu.edu>
cc: freebsd-current@FreeBSD.org
Subject: Re: Can't assign irq for integrated wireless NIC
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Mar 2004 02:30:15 -0000

Good evening.

On Tuesday 02 March 2004 10:47, John Baldwin wrote:
> On Monday 01 March 2004 08:16 pm, Yevgen Muntyan wrote:
> > On Monday 01 March 2004 16:30, John Baldwin wrote:
> > > Can you do 'sysctl debug.bootverbose=1' before kldload'ing ndis.ko and
> > > then send the messages here?
> 
> There should be messages regarding PCI interrupt routing that happen when you 
> kldload ndis.ko when bootverbose is set.
> 

I'm sorry, but there were no messages at all. I did:

sysctl debug.bootverbose=1
kldload ndis

And nothing, module is silently loaded without any messages; kldstat shows 
presense of ndis.ko. ('kldload if_ndis' after that - panic).

Can I do something else?

Yevgen