Date: Fri, 24 Jan 2014 11:52:00 +0000 (UTC) From: "Thomas Mueller" <mueller6724@bellsouth.net> To: freebsd-current@freebsd.org Cc: Adrian Chadd <adrian@freebsd.org>, Miguel Clara <miguelmclara@gmail.com> Subject: Re: Freebsd 11 current testing ndis / kldload: bcmwl564_sys.ko PANIC Message-ID: <610447.24251.bm@smtp117.sbc.mail.gq1.yahoo.com> References: <CADGo8CVGhPXvho-xSfJAjLxe5rc%2B4QYPCJLcDHjmQRogDZNntA@mail.gmail.com> <CAJ-VmoknZioM8mWFFJEdJgKeB6ixQFFqyyQAZgX-ALB-iHLKEg@mail.gmail.com> <CADGo8CUyayK05zC9oJQfMd69rW6noytJrDqGgEa-LQaudvOEbA@mail.gmail.com> <CAJ-VmokZZ6em=P%2Bm-eKB6AexNc14pP9axA9EuxD8vHYcapJFxQ@mail.gmail.com> <CADGo8CUpTvuBya2aF4P5DUhVLfjg0c%2BR3enNW=YdqOeWUCeN3g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?610447.24251.bm>