Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 Jan 2008 14:11:26 +0900
From:      Weongyo Jeong <weongyo.jeong@gmail.com>
To:        Diego Giagio <dgiagio@gmail.com>
Cc:        freebsd-hackers@freebsd.org, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Re: NDIS debugging
Message-ID:  <20080115051126.GA42277@freebsd.weongyo.org>
In-Reply-To: <1b0798830801130752k4209bce7yc5e1cbec7dd67f82@mail.gmail.com>
References:  <1b0798830801130752k4209bce7yc5e1cbec7dd67f82@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jan 13, 2008 at 12:52:01PM -0300, Diego Giagio wrote:
> Hi,
> 
> Recently i've bought a new laptop (Dell Precision M2300) which came
> with Intel 4965 Wifi chipset. Since there's no native driver available
> yet, I've been trying to get it to work throught Project Evil (NDIS
> Windows Driver NETw4x64).
> 
> At first, the driver complained for "no match for
> InitializeSListHead". Then I figured it out how to implement that
> function (a simple bzero on slist_head, just like ndiswrapper on
> Linux) and it stopped complaining. I'm able to kldload NETx4x64_sys.ko
> with success, but it stays silent. It just loads two dependent modules
> (if_nids.ko and nids.ko) and nothing is printed into dmesg or console.
> Also, there's no ndis0 device.
> 
> As far as I can get I could see that DriverEntry()'s module is working
> OK as it returns STATUS_SUCCESS on subr_windrv.c's windrv_load().
> 
> So, the question is: Is there a way to turn on verbose debugging on
> the NDIS subsystem? Would be great if I could get some more info on
> what's going wrong.

As far as I know, there is no verbose debugging mode on the NDIS
subsystem.  Only a variable `ndis_debug' which is defined in if_ndis.c
can be available to turn on `if_ndis' module's debugging mode.

regards,
Weongyo Jeong




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080115051126.GA42277>