(This email contains my conversation history with Pavel, where I
accidentally didn't CC the list.)
Scanning is a passive operation, so most likely it doesn't transmit, just
like my card. Maybe you should try a wireless-testing kernel, and experiment
with ieee80211_regdom. I hope that helps.
On
An idea: Are you using a kernel with SMP and/or PAE enabled? I suspect an
SMP-related issue (I got this problem with OpenSUSE kernels, which are all
SMP-enabled), or maybe HPET/high-resolution timer/tickless system related.
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
wpa_supplicant seems to find a suitable AP and it is requesting kernel
(mac80211 in this case) to associate. However, that is timing out.
wpa_supplicant does not has visibility to what mac80211 does here, so
the next step would be to debug what is happening there (first step
might be to just
Le Wednesday 26 March 2008 13:55:39 Johannes Berg, vous avez écrit :
Just to expand on that, you need to enable mac80211 debugging to get
decent output for this case, and it is well possible that it's still a
driver problem if mac80211 is transmitting packets to the driver but
they never make
On Wed, 2008-03-26 at 13:46 +0100, Stefanik Gábor wrote:
An idea: Are you using a kernel with SMP and/or PAE enabled? I suspect
an SMP-related issue (I got this problem with OpenSUSE kernels, which
are all SMP-enabled), or maybe HPET/high-resolution timer/tickless
system related.
I'm not sure
I think Larry received the first part of my answer directly. was
just a copy of my wpa_supplicant.conf and the debug outputs with both
b43 and bcm43xx.
Is it possible for you to use NetworkManager to control your network
interfaces? If so, please try it that way. NM should set up
Jouni and Johannes,
The correspondent below has a problem authenticating when using the
b43 driver with mac80211, but all works with bcm43xx/SoftMAC. As far
as I can tell, the problem driver is transmitting and receiving, but
still no go. Please look at the wpa_supplicant -ddd output posted at
http://pastebin.org/25229 for b43, and
that doesn't seem to exist any more.
johannes
signature.asc
Description: This is a digitally signed message part
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
On Tuesday 25 March 2008 16:39:23 Larry Finger wrote:
Jouni and Johannes,
The correspondent below has a problem authenticating when using the
b43 driver with mac80211, but all works with bcm43xx/SoftMAC. As far
as I can tell, the problem driver is transmitting and receiving, but
still no
Le Tuesday 25 March 2008 16:59:29 Michael Buesch, vous avez écrit :
On Tuesday 25 March 2008 16:39:23 Larry Finger wrote:
Jouni and Johannes,
The correspondent below has a problem authenticating when using the
b43 driver with mac80211, but all works with bcm43xx/SoftMAC. As far
as I can
Quoting Michael Buesch [EMAIL PROTECTED]:
Which version of wpa_supplicant is this? Can you try latest stable?
Here are the results with wpa_supplicant 0.6.3 :
bcm43xx : http://pastebin.org/25286
b43 : http://pastebin.org/25289
___
Bcm43xx-dev
On Mon, 2008-03-24 at 19:49 -0700, Larry Finger wrote:
The problem is with authentication. The interface is actively
scanning, thus transmit is working.
How do you know that? Receiving beacons doesn't require transmission.
Just trying to understand your logic.
--
Regards,
Pavel Roskin
(Re-posting, since I forgot to confirm)
Hello,
After two monthes trying to find a solution, I'll post directly on the bcm43xx
ML.
- The Launchpad bug is there :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182716 (this thread is
confusing and solves different issues but not the main
The end of the message had a problem, here it is, sorry :
Finally dmesg :
[481907.430896] eth0: Initial auth_alg=0
[481907.430907] eth0: authenticate with AP ba:fa:e6:72:e9:0c
[481907.629997] eth0: authenticate with AP ba:fa:e6:72:e9:0c
[481907.830001] eth0: authenticate with AP ba:fa:e6:72:e9:0c
krop wrote:
(Re-posting, since I forgot to confirm)
Hello,
After two monthes trying to find a solution, I'll post directly on the
bcm43xx ML.
- The Launchpad bug is there :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/182716 (this thread
is confusing and solves different
Selon Larry Finger [EMAIL PROTECTED]:
Despite what is mentionned there :
http://linuxwireless.org/en/users/Drivers/b43#bcm43xx.2Cb43legacy.2Cb43.2Csoftmac.2C...thefullstory
, this card (Linksys WMP-54G pci) doesn't work with b43legacy but b43.
This is exactly what is expected. The
krop wrote:
Selon Larry Finger [EMAIL PROTECTED]:
Despite what is mentionned there :
http://linuxwireless.org/en/users/Drivers/b43#bcm43xx.2Cb43legacy.2Cb43.2Csoftmac.2C...thefullstory
, this card (Linksys WMP-54G pci) doesn't work with b43legacy but b43.
This is exactly what is expected.
If wpa_supplicant shows up in a 'ps ax' output, kill it and restart
from a root-privileged command using the command
wpa_supplicant -Dwext -ieth0 -c/etc/wpa_supplicant.conf -ddd
and send the resulting console output. You may have to issue an 'ifup
eth0' command on another terminal.
Larry
If wpa_supplicant shows up in a 'ps ax' output, kill it and restart
from a root-privileged command using the command
wpa_supplicant -Dwext -ieth0 -c/etc/wpa_supplicant.conf -ddd
and send the resulting console output. You may have to issue an 'ifup
eth0' command on another terminal.
Thank
krop wrote:
If wpa_supplicant shows up in a 'ps ax' output, kill it and restart
from a root-privileged command using the command
wpa_supplicant -Dwext -ieth0 -c/etc/wpa_supplicant.conf -ddd
and send the resulting console output. You may have to issue an 'ifup
eth0' command on another
20 matches
Mail list logo
