Date: Mon, 11 Jan 2010 14:15:45 -0500 From: Bob Johnson <fbsdlists@gmail.com> To: Paul B Mahol <onemda@gmail.com> Cc: FreeBSD Questions <questions@freebsd.org> Subject: NDIS panics (Was: Can I rescan for new PCI devices? Or should hotplugging Expresscards work?) Message-ID: <54db43991001111115y7acaf4ect4a033e43a6ec159@mail.gmail.com>
next in thread | raw e-mail | index | archive | help
On 1/9/10, Paul B Mahol <onemda@gmail.com> wrote: > On 12/16/09, Bob Johnson <fbsdlists@gmail.com> wrote: >> I'm using an ExpressCard for wireless networking because there seems >> to be no driver for the internal card in my laptop (and NDIS panics >> the system). The Expresscard shows up as a PCI device and works fine, > > How are you using NDIS and when system panic what is displayed? I tried to use ndisgen with the internal Dell 1397 card. I don't have details available right now, although if you need them I can try it again. When I did the kldload the system spit out error messages about unknown symbols and then panic-ed. I did some searching of the archives and found a message describing the same symptoms, and the response posted was that it indicated that the Windows driver made API calls that were not implemented in the NDIS wrapper. This was a 64-bit Windows driver and an amd64 FreeBSD system. Similar results in both FreeBSD 7.2 and 8.0. It appears that kern/132672 is describing the same or a very similar issue. It also suggests that there is a more fundamental problem than the unrecognized symbols. I can try to reproduce the problem tonight if you want me to. Thanks, -- -- Bob Johnson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54db43991001111115y7acaf4ect4a033e43a6ec159>