Date: Tue, 2 Mar 2004 11:47:50 -0500 From: John Baldwin <jhb@FreeBSD.org> To: Yevgen Muntyan <muntyan@tamu.edu> Cc: freebsd-current@freebsd.org Subject: Re: Can't assign irq for integrated wireless NIC Message-ID: <200403021147.50480.jhb@FreeBSD.org> In-Reply-To: <200403011916.17683.muntyan@tamu.edu> References: <200402291903.20499.muntyan@tamu.edu> <200403011730.00767.jhb@FreeBSD.org> <200403011916.17683.muntyan@tamu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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? > > I'm sorry, but I don't really understand what messages. As I understand > debug.bootverbose makes logging on startup more verbose, so I don't > understand how does it relate to loading module. Or I need to load module > using loader.conf? Or you need dmesg? It was in my previous letter (and I > put it here). > > Any way, I did "sysctl debug.bootverbose=1" and put "boot_verbose="yes" in > loader.conf, and loaded ndis and if_ndis modules both via loader.conf and > after startup using kldload, and result is always the same - panic with the > same messages. Do you need some info from debugger or something? There should be messages regarding PCI interrupt routing that happen when you kldload ndis.ko when bootverbose is set. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403021147.50480.jhb>