Re: 3com wireless pccard

From: Ben Kaduk (minimarmot_at_gmail.com)
Date: 09/15/05

  • Next message: Robert Watson: "Re: LOR in /usr/src/sys/netinet/in.c:972" 
    Date: Thu, 15 Sep 2005 18:34:38 +0000
To: Bachilo Dmitry <root@solink.ru>

    On 9/15/05, Bachilo Dmitry <root@solink.ru> wrote:
    >
    > Hello
    >
    > I am having a problem with my 3com card. On my 5.4 i had to compile NDIS
    > drivers using original Windows XP drivers presented on drivers disk
    > included
    > in this 3Com wirless device box. And it worked fine.
    >
    > Now the system still compiles with device ndis and options NDISAPI but it
    > writes cardbus0: <network, ethernet> at device 0.0 (no driver attached)
    > instead of creating ndis0 device.
    >
    > By the way device ath and device ath_hal do not compile since 5.4, but
    > that's
    > other story, because this driver actually does not suppord my NIC.
    >
    > Did I miss something about ndis in 6.0-CURRENT or do i do something wrong?
    >
    > Best regards, Bachilo Dmitry.
    > _______________________________________________
    > freebsd-current@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-current
    > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
    >

    The way the ndis driver works has been changed -- the ndis option/module
    only generates infrastructure, it doesn't pull in the actual windows drivers
    anymore -- a separate utility (shell script) ndisgen is now used for this.
    Just type ndisgen at a root prompt and it should be fairly self-explanatory.
    This change allows the ndis framework to support more than one type of
    windows driver at a time -- I have a BCMWL5_SYS.ko module for my wireless
    card, but I could also have a bcm4324.ko module for my onboard card (which
    is actually natively supported) and use them both at the same time. It is my
    understanding that such dual-use was not possible before this change.
    Unfortunately, the documentation of this change is not in a prominent place
    (I missed it myself).

    Hope this solves your problem

    Ben Kaduk
    _______________________________________________
    freebsd-current@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-current
    To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"

  • Next message: Robert Watson: "Re: LOR in /usr/src/sys/netinet/in.c:972"

    Relevant Pages

    • Re: Running NDISTest on Vista with an NDIS IM Driver
      ... Currenty there are no logo programs or tests that test any NDIS IM drivers. ... I tried using the version that comes with WLK/DTM on PassThru (NDIS IM ... Loaded Module Info: ...
      (microsoft.public.development.device.drivers)
    • Re: How to check if a spin lock has been freed or released?
      ... >> they're writing Windows drivers, ... Both on NDIS as well as on if or how other people make ... I think you assumed that I'm a Windows driver developer. ... I said that I wrote the FreeBSD NDIS emulator (or "NDIS ...
      (microsoft.public.development.device.drivers)
    • Re: ndis with USB wifi dongle - no joy
      ... No ndis interface is created, and dmesg shows the following messages: ... Windows NDIS device drivers work because the co-called Project Evil is ...
      (freebsd-questions)
    • Re: How to check if a spin lock has been freed or released?
      ... writing a compatible NDIS for a different operating system and debugging ... buggy NDIS drivers. ... "for evil" and writes drivers that will break unless spinlocks are ... >> they're writing Windows drivers, ...
      (microsoft.public.development.device.drivers)
    • Re: How to check if a spin lock has been freed or released?
      ... > they're writing Windows drivers, ... Both on NDIS as well as on if or how other people make ...
      (microsoft.public.development.device.drivers)