Gábor, Larry
first of all, excuse me for my mistake: I forget to add in Cc: the ml.
The actual situation is:
## /etc/modprobe.d/b43.conf ##
options b43 pio=0 qos=0 nohwcrypt=1
I remove network-manager and gnome-network-manager
It seems to recognize correctly the access point:
## iwconfig ##
wlan0 IEEE 802.11bg ESSID:"XXXXX"
Mode:Managed Frequency:2.472 GHz Access Point:
00:18:4D:2E:85:4A
Bit Rate=1 Mb/s Tx-Power=20 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-21 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
## ifconfig ##
wlan0 Link encap:Ethernet HWaddr 00:1d:60:e7:53:b8
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::21d:60ff:fee7:53b8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:49 errors:0 dropped:0 overruns:0 frame:0
TX packets:91 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4471 (4.3 KiB) TX bytes:12226 (11.9 KiB)
but the ping is very horrible and the connection is unstable:
ING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_req=1 ttl=64 time=2180 ms
64 bytes from 192.168.0.2: icmp_req=3 ttl=64 time=888 ms
64 bytes from 192.168.0.2: icmp_req=5 ttl=64 time=1030 ms
64 bytes from 192.168.0.2: icmp_req=6 ttl=64 time=227 ms
64 bytes from 192.168.0.2: icmp_req=9 ttl=64 time=215 ms
64 bytes from 192.168.0.2: icmp_req=11 ttl=64 time=5100 ms
64 bytes from 192.168.0.2: icmp_req=12 ttl=64 time=4095 ms
64 bytes from 192.168.0.2: icmp_req=14 ttl=64 time=3546 ms
64 bytes from 192.168.0.2: icmp_req=17 ttl=64 time=528 ms
64 bytes from 192.168.0.2: icmp_req=18 ttl=64 time=5875 ms
64 bytes from 192.168.0.2: icmp_req=20 ttl=64 time=3862 ms
64 bytes from 192.168.0.2: icmp_req=21 ttl=64 time=3328 ms
64 bytes from 192.168.0.2: icmp_req=24 ttl=64 time=313 ms
24 packets transmitted, 13 received, 45% packet loss, time 23128ms
rtt min/avg/max/mdev = 215.307/2399.514/5875.790/1923.942 ms, pipe 6
After a few minutes i retry pinging:
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_req=1 ttl=64 time=17.4 ms
64 bytes from 192.168.0.2: icmp_req=2 ttl=64 time=1.82 ms
64 bytes from 192.168.0.2: icmp_req=3 ttl=64 time=5.26 ms
64 bytes from 192.168.0.2: icmp_req=4 ttl=64 time=10.1 ms
64 bytes from 192.168.0.2: icmp_req=5 ttl=64 time=5.63 ms
64 bytes from 192.168.0.2: icmp_req=6 ttl=64 time=1.82 ms
64 bytes from 192.168.0.2: icmp_req=7 ttl=64 time=7.99 ms
64 bytes from 192.168.0.2: icmp_req=8 ttl=64 time=1.98 ms
64 bytes from 192.168.0.2: icmp_req=9 ttl=64 time=2.23 ms
64 bytes from 192.168.0.2: icmp_req=10 ttl=64 time=5.80 ms
64 bytes from 192.168.0.2: icmp_req=11 ttl=64 time=1.83 ms
64 bytes from 192.168.0.2: icmp_req=12 ttl=64 time=35.1 ms
--- 192.168.0.2 ping statistics ---
12 packets transmitted, 12 received, 0% packet loss, time 11016ms
And this time it was perfect!!
Third time:
64 bytes from 192.168.0.2: icmp_req=1 ttl=64 time=9.88 ms
64 bytes from 192.168.0.2: icmp_req=2 ttl=64 time=5.27 ms
64 bytes from 192.168.0.2: icmp_req=3 ttl=64 time=18.9 ms
64 bytes from 192.168.0.2: icmp_req=4 ttl=64 time=0.563 ms
64 bytes from 192.168.0.2: icmp_req=5 ttl=64 time=9.98 ms
64 bytes from 192.168.0.2: icmp_req=9 ttl=64 time=9.71 ms
64 bytes from 192.168.0.2: icmp_req=10 ttl=64 time=20.1 ms
64 bytes from 192.168.0.2: icmp_req=11 ttl=64 time=39.0 ms
64 bytes from 192.168.0.2: icmp_req=12 ttl=64 time=98.7 ms
64 bytes from 192.168.0.2: icmp_req=14 ttl=64 time=137 ms
64 bytes from 192.168.0.2: icmp_req=16 ttl=64 time=197 ms
35 packets transmitted, 21 received, 40% packet loss, time 34115ms
rtt min/avg/max/mdev = 0.563/36.300/197.480/54.568 ms
Now, without any modification:
# ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
>From 192.168.0.100 icmp_seq=1 Destination Host Unreachable
>From 192.168.0.100 icmp_seq=2 Destination Host Unreachable
>From 192.168.0.100 icmp_seq=3 Destination Host Unreachable
^C
--- 192.168.0.2 ping statistics ---
4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 3016ms
pipe 3
And dmesg says:
...
[ 1118.476545] No probe response from AP 00:18:4d:2e:85:4a after 500ms,
disconnecting.
[ 1118.576284] cfg80211: Calling CRDA to update world regulatory domain
[ 1151.048261] wlan0: direct probe to 00:18:4d:2e:85:4a (try 1)
[ 1151.248035] wlan0: direct probe to 00:18:4d:2e:85:4a (try 2)
[ 1151.448024] wlan0: direct probe to 00:18:4d:2e:85:4a (try 3)
[ 1151.648023] wlan0: direct probe to 00:18:4d:2e:85:4a timed out
..
I'm using wpa_supplicant with wpa2 authentication Could be this the problem?
Thanks again for supporting me.
2010/6/22 Larry Finger <[email protected]>
> On 06/21/2010 06:22 PM, Gábor Stefanik wrote:
> > 2010/6/22 Fabrizio Regalli <[email protected]>:
> >> Ok, I put "options b43 pio=0 qos=0" in /etc/modprobe.d/b43.conf
> >> And now the message is changed:
> >>
> >>
> >> ...
> >> [ 745.708045] b43-phy1: Loading firmware version 410.2160 (2007-05-26
> >> 15:32:10)
> >> [ 745.724051] b43-phy1 debug: Chip initialized
> >> [ 745.724189] b43-phy1 debug: 32-bit DMA initialized
> >> [ 745.724198] b43-phy1 debug: QoS disabled
> >> [ 745.744374] b43-phy1 debug: Wireless interface started
> >> [ 745.768105] b43-phy1 debug: Adding Interface type 2
> >> [ 745.796352] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >> [ 748.160267] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)
> >> [ 748.161313] wlan0: authenticated
> >> [ 748.161425] wlan0: associate with 00:18:4d:2e:85:4a (try 1)
> >> [ 748.162831] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431
> >> status=0 aid=1)
> >> [ 748.162835] wlan0: associated
> >> [ 748.163348] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> >> [ 748.168313] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local
> >> choice (reason=3)
> >> [ 748.168466] cfg80211: Calling CRDA to update world regulatory domain
> >> [ 749.496214] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)
> >> [ 749.497126] wlan0: authenticated
> >> [ 749.497240] wlan0: associate with 00:18:4d:2e:85:4a (try 1)
> >> [ 749.498655] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431
> >> status=0 aid=1)
> >> [ 749.498659] wlan0: associated
> >> [ 749.504316] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local
> >> choice (reason=3)
> >> [ 749.504523] cfg80211: Calling CRDA to update world regulatory domain
> >>
> >>
> >> But unfortunately does not work.
> >>
> >> I can obtain just the ip address:
> >>
> >> # ifconfig wlan0 |grep inet
> >> inet addr:192.168.0.100
> >>
> >> but iwconfig show me there isn't any access point associeted:
> >>
> >> wlan0 IEEE 802.11bg ESSID:off/any
> >> Mode:Managed Frequency:2.472 GHz Access Point:
> Not-Associated
> >> Tx-Power=20 dBm
> >> Retry long limit:7 RTS thr:off Fragment thr:off
> >> Encryption key:off
> >> Power Management:off
> >>
> >>
> >
> > Did you shut down NetworkManager?
> >
> > Also, why are you disabling QoS? Unless you are using OpenFWWF, QoS
> > shouldn't need to be disabled.
>
> I will describe some recent findings in a separate email; however, to use
> the BCM4312 in PIO mode, you do need to disable QoS AND hardware
> encryption. Add "nohwcrypt=1" to b43.conf and leave the "qos=0" in.
>
> Larry
>
>
_______________________________________________
b43-dev mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/b43-dev
