Re: bcm43xx with 2.6.21 vanilla and larry's combined patch loops - SOLVED
Jörg Sommer wrote: > Hallo Larry, > > Larry Finger <[EMAIL PROTECTED]> wrote: >> Denis V Seleznyov wrote: >>> On Sunday, 06 May 2007 04:11:49 Denis V Seleznyov wrote: Ehud Gavron wrote: > The bcm43xx modules reports associated... scanning... associated... with > another message in the middle, about once every half second without > stopping. > The dmesg shows radio on, link not ready, link associated, radio off, > [repeats] I have similar problem with 4311 (Dell Inspiron 640m with 1390 mini-wireless module). I didn't noticed neither any problems with kernel module inserting or removing, nor kernel panic. Network authentication: WPA-PSK with TKIP encryption >>> I don't know how it did happen, but CONFIG_IEEE80211_CRYPT_TKIP was not set. >>> >>> Thus, it is bug in wpa_supplicant or softmac code rather then in bcm43xx. >> This is an operator problem, not a bug. Neither the bcm43xx nor the >> softmac code has any way to know that you wish to use TKIP >> authentication. > > Doesn't wpa_supplicant tell softmac it wants TKIP? Then softmac can > report it doesn't support TKIP. It isn't softmac, it is ieee80211. The following messages were the error indicating that the TKIP modules was not available.: ioctl[SIOCSIWENCODEEXT]: Invalid argument Driver did not support SIOCSIWENCODEEXT WPA: Failed to set PTK to the driver. If you think the error message should be stronger, talk to the Intel guys as they are the maintainers of the ieee80211 component. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Merging SSB upstream
On Sunday 06 May 2007 19:38:33 John W. Linville wrote: > On Sun, May 06, 2007 at 11:44:27AM +0200, Michael Buesch wrote: > > On Sunday 06 May 2007 04:00:51 John W. Linville wrote: > > > > I had to remove > > > the b44 ssb changes from fedora because a) users reported problems; > > > > Which problems were that? The 2 compile issues? > > Trivial to fix if that's the only issue. ;) > > I knew you would ask that... :-) :P > I don't think there was a bugzilla, but Dave Jones forwarded an email > to me from "MASAO TAKAHASHI" in late February. Takahashi-san (forgive > me if I did that wrong) was complaining about tx timeouts after I > had added the full wireless-dev patchset to rawhide. Removing the > b44 bits of the patch seemed to remove the problem. > > That's all the info I have. Perhaps Dave or Takahashi-san can add > to the description? Hm, interesting issue. But I'm not convinced that it's caused by the SSB port, though. What the SSB port essentially does is modifying small areas in the init and exit paths. The modified things in the TX and RX hotpaths are really tiny and trivial. TX timeout sounds like something in the TX/RX paths is going wrong. But anyway, maybe I got something wrong. I'll run some burn-in tests on it now. -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Merging SSB upstream
On Sun, May 06, 2007 at 11:44:27AM +0200, Michael Buesch wrote: > On Sunday 06 May 2007 04:00:51 John W. Linville wrote: > > I had to remove > > the b44 ssb changes from fedora because a) users reported problems; > > Which problems were that? The 2 compile issues? > Trivial to fix if that's the only issue. ;) I knew you would ask that... :-) I don't think there was a bugzilla, but Dave Jones forwarded an email to me from "MASAO TAKAHASHI" in late February. Takahashi-san (forgive me if I did that wrong) was complaining about tx timeouts after I had added the full wireless-dev patchset to rawhide. Removing the b44 bits of the patch seemed to remove the problem. That's all the info I have. Perhaps Dave or Takahashi-san can add to the description? John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm43xx with 2.6.21 vanilla and larry's combined patch loops - SOLVED
Hallo Larry, Larry Finger <[EMAIL PROTECTED]> wrote: > Denis V Seleznyov wrote: >> On Sunday, 06 May 2007 04:11:49 Denis V Seleznyov wrote: >>> Ehud Gavron wrote: The bcm43xx modules reports associated... scanning... associated... with another message in the middle, about once every half second without stopping. The dmesg shows radio on, link not ready, link associated, radio off, [repeats] >>> I have similar problem with 4311 (Dell Inspiron 640m with 1390 >>> mini-wireless module). I didn't noticed neither any problems with kernel >>> module inserting or removing, nor kernel panic. >> >>> Network authentication: WPA-PSK with TKIP encryption >> >> I don't know how it did happen, but CONFIG_IEEE80211_CRYPT_TKIP was not set. >> >> Thus, it is bug in wpa_supplicant or softmac code rather then in bcm43xx. > > This is an operator problem, not a bug. Neither the bcm43xx nor the > softmac code has any way to know that you wish to use TKIP > authentication. Doesn't wpa_supplicant tell softmac it wants TKIP? Then softmac can report it doesn't support TKIP. Bye, Jörg. -- Damit das Mögliche entsteht, muß immer wieder das Unmögliche versucht werden. (Hermann Hesse) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Merging SSB upstream
On Sunday 06 May 2007 04:00:51 John W. Linville wrote: > On Sun, May 06, 2007 at 03:03:17AM +0200, Michael Buesch wrote: > > So, now that mac80211 is merged upstream, I think it's > > time to merge SSB and the b44-ssb port upstream. > > Note that bcm43xx-mac80211 is _not_ ready for upstream, yet. > > ACK, unfortunately. > > > What do you think? I'd like to merge ssb as-is, although > > the embedded-device parts are not quite finished, yet. > > But they don't interfere with the non-embedded parts used > > by b44 and the bcm43xx PCI cards. > > How much testing have you (and others) done w/ b44? Well, it works for me with my b44 card I got from broadcom. There are really only 2 or 3 different b44 cards, so chances are damn high it will work for all. > I had to remove > the b44 ssb changes from fedora because a) users reported problems; Which problems were that? The 2 compile issues? Trivial to fix if that's the only issue. ;) -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Merging SSB upstream
On Sunday 06 May 2007 05:11:44 Jeff Garzik wrote: > Michael Buesch wrote: > > So, now that mac80211 is merged upstream, I think it's > > time to merge SSB and the b44-ssb port upstream. > > Note that bcm43xx-mac80211 is _not_ ready for upstream, yet. > > > > What do you think? I'd like to merge ssb as-is, although > > the embedded-device parts are not quite finished, yet. > > But they don't interfere with the non-embedded parts used > > by b44 and the bcm43xx PCI cards. > > So we _could_ remove the ssb-mips code, but I don't like to > > do that for better maintainability. It doesn't hurt anyone IMO. > > What does Ralf (MIPS maintainer) and Gary (Broadcom maintainer) think? I don't know. I wanted to get all these opinions with this mail. :) > For my part, I'm not going to render even a tentative opinion without a > link to actual code. All code is in wireless tree drivers/ssb http://bu3sch.de/gitweb?p=wireless-dev.git;a=tree;f=drivers/ssb;h=681cd93bf166670efbdec471b78137d3d0f26537;hb=HEAD -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
