From owner-freebsd-current@FreeBSD.ORG  Mon Mar  8 03:13:09 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 0DF9116A4CE; Mon,  8 Mar 2004 03:13:09 -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 9AD6943D2D; Mon,  8 Mar 2004 03:13:06 -0800 (PST)
	(envelope-from muntyan@tamu.edu)
Received: from mlap ([66.233.123.200]) by fe5.cox-internet.com
	ac98e04b23802b25ff26d48c352bda07)
	with ESMTP id <20040308111306.NJMO377.fe5@mlap>;
	Mon, 8 Mar 2004 05:13:06 -0600
From: Yevgen Muntyan <muntyan@tamu.edu>
To: John Baldwin <jhb@freebsd.org>
Date: Mon, 8 Mar 2004 05:13:08 -0600
User-Agent: KMail/1.6
References: <200402291903.20499.muntyan@tamu.edu>
	<200403022030.09432.muntyan@tamu.edu> <200403031434.26621.jhb@FreeBSD.org>
In-Reply-To: <200403031434.26621.jhb@FreeBSD.org>
MIME-Version: 1.0
Content-Disposition: inline
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Message-Id: <200403080513.08110.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: Mon, 08 Mar 2004 11:13:09 -0000

On Wednesday 03 March 2004 13:34, John Baldwin wrote:
> 
> Sorry, it would be the if_ndis.ko that did the messages.  Can you load ndis.ko 
> and if_ndis.ko from the boot loader, do a boot -v and capture that output via 
> a serial console or some such?
> 

Hello,

Sorry for delay, I could not find null-modem cable. I have not found it yet,
but I've made pictures of all screens during boot; I put them on
http://munt.mine.nu:3000/if_ndis.html
Sorry for this, still looking for cable.

Yevgen