NOTE: tried NDISulator

pciconf -lv | grep -i bcm -B2
none2@pci0:13:0:0:      class=0x028000 card=0x145c103c chip=0x472714e4
rev=0x01 hdr=0x00
    vendor     = 'Broadcom Corporation'
    device     = 'BCM4313 802.11b/g/n Wireless LAN Controller'


# ndisload -p -s /home/user/bcmWireless/bcmwl564.sys -n bcmw -v 0x14e4 -d 0x4721


and get this in dmesg:

NDIS: no match for ZwQueryInformationFile


I'll report it in the github page, but it seems its not working!


# tail /var/log/messages
Jan 24 16:44:37 hpbsd kernel: NDIS: no match for ZwQueryInformationFile
Jan 24 16:46:10 hpbsd kernel: NDIS: no match for ZwQueryInformationFile
Jan 24 16:48:27 hpbsd kernel: Warning: memory type ndis_ntoskrnl
leaked memory on destroy (8 allocations, 2304 bytes leaked).

On Fri, Jan 24, 2014 at 1:59 PM, Adrian Chadd <adr...@freebsd.org> wrote:
> ... who's the author of this? Why aren't they posting updates to
> FreeBSD-HEAD so it can be included in the base system?
>
> Does anyone have a contact email for the author, Vadislav?
>
>
> -a
>
>
> On 24 January 2014 03:52, Thomas Mueller <mueller6...@bellsouth.net> wrote:
>> To Miguel Clara, you might try a USB wireless adapter.  I use Hiro H50191, 
>> driver rsu.
>>
>> But you would need to do good research to find what the chip is, and which 
>> FreeBSD driver, if any, would it work with, before you buy.
>>
>> NDISulator looks worth trying.  FreeBSD users will want to know if it works.
>>
>> https://github.com/NDISulator/ndisulator
>>
>> Regarding deprecation of NDIS, is it a matter of something that is 
>> compatible with Linux but very difficult to port to BSD?
>>
>> There is the problem with newer MS-Windows drivers that they don't come with 
>> .sys and .inf files, or maybe they have to be unpacked and installed from 
>> MS-Windows.  Then NDIS would have nothing to work with.
>>
>> Tom
>>
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to