/usr/src/sys/dev/netif/ndis/if_ndis.c

Matthew Dillon dillon at apollo.backplane.com
Sun Jan 1 18:33:31 PST 2006


:
:Matthew Dillon wrote:
:>     if_ndis alone will not create an interface.  You have to follow the
:>     instructions in the README to associate a windows device driver
:>     with it.  Then it comes down to it probing the device properly.
:
:	I did follow the instructions and at step four where it states, "you 
:should something similar to the following system console messages:", I 
:get one blank line of output when using Xorg. ifconfig shows no ndis0 
:interface.
:
:	When I'm only using the console and I do the last kldload, I see this 
:error:
:
:Function Extension: ...
:..
:CIS reading done
:ndis0: <Belkin Wireless ... Adapter> mem ... irq 11 at device 0.0 on 
:cardbus1
:can't re-use a leaf (FrameBursting)!
:ndis0: NDIS API version 5.0
:ndis0: NDIS ERROR: c000138d (unknown error)
:ndis0: NDIS NUMERRORS: 1
:ndis0: argptr: 0x103
:ndis0: init handler failed
:device_probe_and_attach: ndis0 attach returned 6

    It looks like an issue that a lot of people have had with that
    device.  Do a google search for "belkin wireless ndis c000138d".
    I'm not sure if there is a fix anywhere.  It could be a firmware
    issue.

					-Matt
					Matthew Dillon 
					<dillon at xxxxxxxxxxxxx>





More information about the Bugs mailing list