DragonFly bugs List (threaded) for 2006-01
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
When I'm only using the console and I do the last kldload, I see this
Function Extension: ...
CIS reading done
ndis0: <Belkin Wireless ... Adapter> mem ... irq 11 at device 0.0 on
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