Date: Sat, 24 Jul 2010 08:42:04 -0400 From: Jerry <freebsd.user@seibercom.net> To: freebsd-questions@freebsd.org Subject: Re: 64-bit Windows XP NDIS drivers giving missing symbols Message-ID: <20100724084204.597b9e6f@scorpio> In-Reply-To: <AANLkTin%2BL3rxWLUGSpzdh4kmJvx43swOJ8E847qjub5t@mail.gmail.com> References: <AANLkTinhc-Qp1jV3TB92BYPf3UxVV7Uf0TJN2X7wwLxt@mail.gmail.com> <AANLkTin%2BL3rxWLUGSpzdh4kmJvx43swOJ8E847qjub5t@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 24 Jul 2010 12:01:24 +0000 Paul B Mahol <onemda@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. -- Jerry ✌ FreeBSD.user@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ Do something unusual today. Pay a bill.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100724084204.597b9e6f>