On Sat, 24 Jul 2010 18:45:24 +0000 Paul B Mahol <one...@gmail.com> articulated:
> On 7/24/10, Jerry <freebsd.u...@seibercom.net> wrote: > > On Sat, 24 Jul 2010 12:01:24 +0000 > > Paul B Mahol <one...@gmail.com> articulated: > > > >> Such symbols are completly irrelevant for normal operation, because > >> NDISulator crash on amd64 during driver initialization. > >> I fixed this in my own git repo, but "fpudna in kernel mode" (my > >> understanding is that it is source of panic when trying to use ndis0 > >> device on amd64), present only on amd64 is still not yet fixed - this > >> should be addressed with fpu_kern KPI available on CURRENT - not done > >> yet... > >> Feel free to send patches. > > > > I feel his pain. I need 64 bit drivers for cards that FBSD does not > > support, mostly 'N' protocol wireless cards. The inability to secure > > and use perfectly good drivers that are available for Windows users in > > FreeBSD is a real PIA. Of course, it does give my Window user friends > > something to laugh about. > > And bwn(4) doesn't work at all? <quote> bwn -- Broadcom BCM43xx IEEE 802.11b/g wireless network driver </quote> You will notice that there is no 'n' in the description. In any case, it is limited to 'broadcom' chips. -- Jerry ✌ freebsd.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"