Re: Lucent IBSS mode doesn't work in -CURRENT?

From: Sam Leffler (sam_at_errno.com)
Date: 07/31/03

  • Next message: Chris Shenton: "Re: make buildworld: Signal 11; Illegal instruction"
    Date: Thu, 31 Jul 2003 11:51:14 -0700
    To: Eirik Oeverby <ltning@anduin.net>, "Greg 'groggy' Lehey" <grog@lemis.com>
    
    

    > I have a few Orinoco cards, and they 'work' in both ad-hoc and
    > infrastructure mode. However with dhclient it gets tricky, because it
    > will only work the first time dhclient assigns an address to the card.
    > Whenever it tries to refresh it or whatever, I start getting those
    > timeout and busy bit errors, and network connectivity drops. This
    > usually happens within a few minutes or latest after 30 minutes or so -
    > probably depending on your dhcpd/dhclient configuration. Configuring a
    > static IP lets me use the card, and it seems stable.
    >

    I recently tested adhoc mode 'cuz Greg said it didn't work and verified it
    worked for me with all my cards: Prism, Lucent (6.something firmware), and
    Atheros (5211, and 5212 in 11b talking to the Lucent and Prism cards).

    I did not use dhclient. Everything was statically configured.

    > I am really glad someone else is seeing this, perhaps it can get fixed
    > some day :)
    >
    > Oh and btw.. Get the *latest* firmware onto all your cards. That is
    > essential for anything to work right at all..
    >

    I'm stuck upgrading because my Windows 2K Lucent driver is too out of date
    for any of the newer firmware revs. I believe I need at least rev 6.1 of
    the Win2K driver to run any of the firmware update tools. How did you
    upgrade your firmware? If anyone has the bits+pieces to rev firmware I'd
    like it so I can test the wi driver w/ different firmware revs.

            Sam

    _______________________________________________
    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: Chris Shenton: "Re: make buildworld: Signal 11; Illegal instruction"

    Relevant Pages

    • ACX100 Firmware Licensing
      ... Compared to other types of hardware, the support for wireless cards ... is lacking on *BSD because many vendors don't provide documentation ... or the cards require the upload of a binary firmware image that, ... help by writing to the hardware vendors. ...
      (freebsd-current)
    • ACX100 Firmware Licensing
      ... Compared to other types of hardware, the support for wireless cards ... is lacking on *BSD because many vendors don't provide documentation ... or the cards require the upload of a binary firmware image that, ... help by writing to the hardware vendors. ...
      (freebsd-questions)
    • RE: [PATCH] Unify sysfs filenames for firmware version
      ... does not fit into the single 'firmware revision' common ideal ... While I've used the aacraid cards in the past I think I agree ... There are 113 cards this driver works for in concert. ...
      (Linux-Kernel)
    • Re: Please suggest a fedora core 4 compatible wireless card
      ... > In some cases - it is the FCC that may actually be at fault. ... > The FCC has regulations on what devices can be user configurable - with ... > This is why some cards have non open firmware that has to be used, ...
      (Fedora)
    • Re: ENE 4-in-1 card reader
      ... : M. Warner Losh wrote: ... you need to do to get the SD/MD/etc flash cards working is to treat ... firmware, but I haven't puzzled out where that firmware comes from or ... Likely something as part of the SD cards, ...
      (freebsd-current)