Re: Lucent IBSS mode doesn't work in -CURRENT?
In message: <[EMAIL PROTECTED]> Eirik Oeverby <[EMAIL PROTECTED]> writes: : To the maintainers: Take your time. Better do it right than do it quick : and dirty. It works in 4.x, and 5.x is not considered stable yet so if : anyone expects everything to work they are in error. It is about a 80% different driver in current than in stable. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lucent IBSS mode doesn't work in -CURRENT?
In message: <[EMAIL PROTECTED]> Brad Knowles <[EMAIL PROTECTED]> writes: : bit annoying, but it seems to me that he's asking a perfectly : legitimate question -- if things worked fine in the past (including : the firmware versions at the time), and they don't work now, then why : is a firmware update needed? The problem is that the driver maintainers know it is a problem, know that newer firmware is a workaround and haven't had the time to find and fix the underlying bug. Having people say that it isn't a fix only a workaround repeatedly is annoying, since that's the position we've taken from the get go. The driver was massively rewritten to speed up intersil cards. The reason that a firmware update is needed is that the old driver worked around bugs in the firmware, but the new driver doesn't. The new driver tries to increase performance on prism cards by using newer features of the firmware. These features aren't present in the older wavelan firmwares. Trouble is, I'm not exactly sure which of the new, cool things causes the problems. I've already identified 3 or 4, which makes some lucent cards work on some systems, but I don't know the others. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lucent IBSS mode doesn't work in -CURRENT?
Sorry, I missed the point that it had once worked. However, the point still needs to be made that in the past I have had varying success with various firmware revisions, but the latest revision is the only one that has worked everywhere I have tried it. Good thing I didn't install the kernel I built yesterday, if that means my wi-driven lucent card would stop working =) To the maintainers: Take your time. Better do it right than do it quick and dirty. It works in 4.x, and 5.x is not considered stable yet so if anyone expects everything to work they are in error. /Eirik On Mon, 4 Aug 2003 19:15:54 +0930 Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote: > On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote: > > At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: > > > >> In message: <[EMAIL PROTECTED]> > >> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: > >> > >>> On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: > > Oh and btw.. Get the *latest* firmware onto all your cards. That > >is>>> essential for anything to work right at all.. > >>> > >>> That sounds wrong to me. If it worked before, and it doesn't now, > >>> that's not the fault of the firmware. > >> > >> Quit harping on it, ok. We know there's a bug and carping like > >this> makes me less willing to find and fix it. > > > > I'm confused. I agree that I have sometimes found Greg to be a > > bit annoying, but it seems to me that he's asking a perfectly > > legitimate question -- if things worked fine in the past (including > > the firmware versions at the time), and they don't work now, then > > why is a firmware update needed? > > > > I would ask: > > > > What changed so that things broke, and why can't we go back > > to the way things worked before? > > I think you're misunderstanding Warner. He's not disagreeing. My > message wasn't directed at Warner, it was directed at Eirik. > > Greg > -- > See complete headers for address and phone numbers > pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
On Monday, 4 August 2003 at 11:37:44 +0200, Brad Knowles wrote: > At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: > >> In message: <[EMAIL PROTECTED]> >> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> >>> On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: Oh and btw.. Get the *latest* firmware onto all your cards. That is essential for anything to work right at all.. >>> >>> That sounds wrong to me. If it worked before, and it doesn't now, >>> that's not the fault of the firmware. >> >> Quit harping on it, ok. We know there's a bug and carping like this >> makes me less willing to find and fix it. > > I'm confused. I agree that I have sometimes found Greg to be a > bit annoying, but it seems to me that he's asking a perfectly > legitimate question -- if things worked fine in the past (including > the firmware versions at the time), and they don't work now, then why > is a firmware update needed? > > I would ask: > > What changed so that things broke, and why can't we go back > to the way things worked before? I think you're misunderstanding Warner. He's not disagreeing. My message wasn't directed at Warner, it was directed at Eirik. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
At 11:51 PM -0600 2003/08/03, M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: : > : > Oh and btw.. Get the *latest* firmware onto all your cards. That is : > essential for anything to work right at all.. : : That sounds wrong to me. If it worked before, and it doesn't now, : that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. I'm confused. I agree that I have sometimes found Greg to be a bit annoying, but it seems to me that he's asking a perfectly legitimate question -- if things worked fine in the past (including the firmware versions at the time), and they don't work now, then why is a firmware update needed? I would ask: What changed so that things broke, and why can't we go back to the way things worked before? Please, this is a serious question. I'm not running 5.x yet on my in-house server/laptop, but I hope to soon (once I get some more servers in the house on which I can be more conservative), and a Lucent WaveLAN gold is definitely one of the things I plan on sticking in there to play with. I really want this to work, and I don't understand how we got to the situation we're in today. Can you explain things to me, perhaps in a somewhat simpler fashion, so that I might understand, and maybe even help? -- Brad Knowles, <[EMAIL PROTECTED]> "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lucent IBSS mode doesn't work in -CURRENT?
On Sunday, 3 August 2003 at 23:51:55 -0600, M. Warner Losh wrote: > In message: <[EMAIL PROTECTED]> > "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: >> On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: >>> Hey, >>> >>> 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 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.. >> >> That sounds wrong to me. If it worked before, and it doesn't now, >> that's not the fault of the firmware. > > Quit harping on it, ok. We know there's a bug and carping like this > makes me less willing to find and fix it. I'm not harping on it, just pointing out that there's a difference between a workaround and a fix. If it hadn't been for that comment, I wouldn't have replied at all. I've borrowed an access point, so I'm not in any pain right now. Let me know if you want me to test something. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
In message: <[EMAIL PROTECTED]> "Greg 'groggy' Lehey" <[EMAIL PROTECTED]> writes: : On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: : > Hey, : > : > 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 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.. : : That sounds wrong to me. If it worked before, and it doesn't now, : that's not the fault of the firmware. Quit harping on it, ok. We know there's a bug and carping like this makes me less willing to find and fix it. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lucent IBSS mode doesn't work in -CURRENT?
On Thursday, 31 July 2003 at 9:30:31 +0200, Eirik Oeverby wrote: > Hey, > > 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 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.. That sounds wrong to me. If it worked before, and it doesn't now, that's not the fault of the firmware. Greg -- See complete headers for address and phone numbers pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
Hi, Are you sure? I believe the Win2k driver is still at the same level as the XP driver - you probably just need to download a newer one.. Correct me if I'm wrong. But I have a Sony Vaio thingie here with Win2k, and I've used that one to upgrade all my cards (Lucent, Orinoco and Avaya labelled - same card, different sticker). Can't recall which firmware version, though. Can I see that from fbsd? /Eirik > > 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 > pgp0.pgp Description: PGP signature
Re: Lucent IBSS mode doesn't work in -CURRENT?
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 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Lucent IBSS mode doesn't work in -CURRENT?
Hey,
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 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..
/Eirik
On Thu, 31 Jul 2003 14:20:30 +0930
Greg 'groggy' Lehey <[EMAIL PROTECTED]> wrote:
> Earlier this month I sent a message saying that my wireless card
> (Orinoco) doesn't work at all any more. In the meantime, I've
> narrowed the problem down to IBSS ("ad-hoc") mode: it works fine in
> BSS (base station) mode. I'd like to know if *anybody* is using IBSS
> (maybe with Orinoco cards) on a -CURRENT newer than about mid-May.
>
> Here's a summary of what I see:
>
> It happens on two different cards with different firmware. The
> ifconfig and wicontrol outputs look identical modulo MAC address and
> IBSS channel.
>
> wi0: flags=8802 mtu 1500
> ether 00:02:2d:04:09:3a
> media: IEEE 802.11 Wireless Ethernet autoselect (none)
> ssid ""
> stationname "FreeBSD WaveLAN/IEEE node"
> channel -1 authmode OPEN powersavemode OFF powersavesleep 100
> wepmode OFF weptxkey 1
>
> NIC serial number: [ ]
> Station name: [ FreeBSD WaveL ]
> SSID for IBSS creation: [ ]
> Current netname (SSID): [ ]
> Desired netname (SSID): [ ]
> Current BSSID: [ 00:00:00:00:00:00 ]
> Channel list: [ 7ff ]
> IBSS channel: [ 3 ]
> Current channel:[ 65535 ]
> Comms quality/signal/noise: [ 0 0 0 ]
> Promiscuous mode: [ Off ]
> Process 802.11b Frame: [ Off ]
> Intersil-Prism2 based card: [ 0 ]
> Port type (1=BSS, 3=ad-hoc):[ 1 ]
> MAC address:[ 00:02:2d:04:09:3a ]
> TX rate (selection):[ 0 ]
> TX rate (actual speed): [ 0 ]
> RTS/CTS handshake threshold:[ 2312 ]
> Create IBSS:[ Off ]
> Access point density: [ 1 ]
> Power Mgmt (1=on, 0=off): [ 0 ]
> Max sleep time: [ 100 ]
> WEP encryption: [ Off ]
> TX encryption key: [ 1 ]
> Encryption keys:[ ][ ][ ][ ]
>
> wi0: at port 0x100-0x13f irq 11
> function 0 config 1 on pccard1 wi0: 802.11 address: 00:02:2d:04:09:3a
> wi0: using Lucent Technologies, WaveLAN/IEEE
> wi0: Lucent Firmware: Station (6.6.1)
> wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>
> wi0: at port 0x100-0x13f irq 11
> function 0 config 1 on pccard1 wi0: 802.11 address: 00:02:2d:1e:d9:60
> wi0: using Lucent Technologies, WaveLAN/IEEE
> wi0: Lucent Firmware: Station (6.16.1)
> wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
>
> When I run dhclient against the first card, I don't get a connection,
> and the other end doesn't see any data traffic, but it finds the
> network:
>
> wi0: flags=8843 mtu 1500
> inet6 fe80::202:2dff:fe04:93a%wi0 prefixlen 64 scopeid 0x4
> inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255
> ether 00:02:2d:04:09:3a
> media: IEEE 802.11 Wireless Ethernet autoselect (DS/2Mbps)
> status: associated
> ssid FOOXX 1:FOOXX
> stationname "FreeBSD WaveLAN/IEEE node"
> channel 3 authmode OPEN powersavemode OFF powersavesleep 100
> wepmode OFF weptxkey 1
>
> I had guessed that it might be turning WEP on without saying so, but
> setting WEP on at both ends didn't help either.
>
> The second card is much worse than the first: when I try to start
> dhclient against it, I get the following messages:
>
> wi0: timeout in wi_cmd 0x0002; event status 0x8080
> wi0: timeout in wi_cmd 0x0121; event status 0x8080
> wi0: wi_cmd: busy bit won't clear.
>
> This last one continues forever. At least the keyboard is locked, so
> I can't do anything (not even get into ddb, which might have been
> useful). While trying to power down I got these messages:
>
> wi0: failed to allocate 2372 bytes on NIC.
> wi0: tx buffer allocateion failed (error 12)
>
> After that, it continued until I finally managed to power down.
>
> Greg
> --
> Finger [EMAIL PROTECTED] for PGP public key
> See complete headers for address and phone numbers
>
pgp0.pgp
Description: PGP sig
