* Problem with b43
@ 2010-05-31 21:45 Fabrizio Regalli
2010-06-01 2:17 ` William Bourque
0 siblings, 1 reply; 24+ messages in thread
From: Fabrizio Regalli @ 2010-05-31 21:45 UTC (permalink / raw)
To: b43-dev
Hello,
I have a problem with b43 driver.
Here's some information of my system (debian sid)
# dmesg |grep b43
[ 2.046367] b43-pci-bridge 0000:04:05.0: PCI INT A -> GSI 17 (level, low)
-> IRQ 17
[ 7.860803] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 8.039770] Registered led device: b43-phy0::tx
[ 8.039784] Registered led device: b43-phy0::rx
[ 8.039797] Registered led device: b43-phy0::assoc
[ 8.039810] Registered led device: b43-phy0::radio
[ 10.672291] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 10.710304] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[ 10.713597] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[ 10.730028] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[ 10.852266] b43-phy0: Loading firmware version 478.104 (2008-07-01
00:50:23)
# uname -a
Linux debiancasa 2.6.34 #1 SMP PREEMPT Mon May 24 22:41:39 CEST 2010 i686
GNU/Linux
# lspci -vvn|grep 43 -A7
04:05.0 0280: 14e4:4318 (rev 02)
Subsystem: 1043:100f
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Latency: 64
Interrupt: pin A routed to IRQ 17
Region 0: Memory@f79f6000 (32-bit, non-prefetchable) [size=8K]
Kernel driver in use: b43-pci-bridge
04:0a.0 0c00: 104c:8023 (prog-if 10 [OHCI])
Subsystem: 1028:0215
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr-
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 64 (500ns min, 1000ns max), Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 18
# lsmod |grep b43
b43 97693 0
mac80211 110180 1 b43
cfg80211 95149 2 b43,mac80211
led_class 1575 1 b43
When I bring up the interface (ifup wlan0)
[12246.900516] b43-phy0: Loading firmware version 478.104 (2008-07-01
00:50:23)
[12246.988328] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[12416.648176] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1)
[12416.848040] wlan0: authenticate with 00:18:4d:2e:85:4a (try 2)
[12417.048048] wlan0: authenticate with 00:18:4d:2e:85:4a (try 3)
[12417.248026] wlan0: authentication with 00:18:4d:2e:85:4a timed out
[12463.932235] wlan0: direct probe to 00:18:4d:2e:85:4a (try 1)
[12464.132034] wlan0: direct probe to 00:18:4d:2e:85:4a (try 2)
[12464.332034] wlan0: direct probe to 00:18:4d:2e:85:4a (try 3)
[12464.532023] wlan0: direct probe to 00:18:4d:2e:85:4a timed out
[12517.684235] wlan0: direct probe to 00:18:4d:2e:85:4a (try 1)
[12517.884034] wlan0: direct probe to 00:18:4d:2e:85:4a (try 2)
[12518.084530] wlan0: direct probe to 00:18:4d:2e:85:4a (try 3)
[12518.284034] wlan0: direct probe to 00:18:4d:2e:85:4a timed out
..and I can't connect to my access point..
My /etc/network/interfaces:
....
# wireless
auto wlan0
iface wlan0 inet static
#wireless-mode managed
wpa-driver wext
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
# static ip settings
address 192.168.0.100
netmask 255.255.255.0
#network 192.168.0.0
#broadcast 192.168.0.255
gateway 192.168.0.1
Could someone plese give me a suggest ?
Thanks a lot.
Fabrizio
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100531/2c7c9f72/attachment.htm>
^ permalink raw reply [flat|nested] 24+ messages in thread* Problem with b43 2010-05-31 21:45 Problem with b43 Fabrizio Regalli @ 2010-06-01 2:17 ` William Bourque 2010-06-01 8:39 ` Martino Salvetti 0 siblings, 1 reply; 24+ messages in thread From: William Bourque @ 2010-06-01 2:17 UTC (permalink / raw) To: b43-dev Just saying, I have a similar problem... I tried to post twice about it on the list since 2 weeks but the mails keep getting moderated (and never unmoderated) because of "suspicious content". - William ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-01 2:17 ` William Bourque @ 2010-06-01 8:39 ` Martino Salvetti 2010-06-20 12:04 ` Fabrizio Regalli 0 siblings, 1 reply; 24+ messages in thread From: Martino Salvetti @ 2010-06-01 8:39 UTC (permalink / raw) To: b43-dev Also me... I sent a message about this problem but it was blocked. I have this problem olny with multi-AP networks, in dmesg I can see that it continue to changes the AP until they ends to responds. (At my home, with a digicom ADSL router, the wifi works) Martino 2010/6/1 William Bourque <william.bourque@polymtl.ca> > > Just saying, I have a similar problem... I tried to post twice about it > on the list since 2 weeks but the mails keep getting moderated (and > never unmoderated) because of "suspicious content". > > - William > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev > -- Remember: with great power comes great current squared times resistance. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100601/b24d8588/attachment.htm> ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-01 8:39 ` Martino Salvetti @ 2010-06-20 12:04 ` Fabrizio Regalli 2010-06-20 18:12 ` Gábor Stefanik 0 siblings, 1 reply; 24+ messages in thread From: Fabrizio Regalli @ 2010-06-20 12:04 UTC (permalink / raw) To: b43-dev I'm trying with an oldest firmware revision but unfortunately, nothing changed. debiancasa:/home/rizla# dmesg |grep b43 [ 2.054445] b43-pci-bridge 0000:04:05.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [ 8.338798] b43-phy0: Broadcom 4318 WLAN found (core revision 9) [ 8.380033] b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 [ 8.380054] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 [ 8.577430] Registered led device: b43-phy0::tx [ 8.577443] Registered led device: b43-phy0::rx [ 8.577455] Registered led device: b43-phy0::assoc [ 8.577470] Registered led device: b43-phy0::radio [ 10.844287] b43 ssb0:0: firmware: requesting b43/ucode5.fw [ 10.924217] b43 ssb0:0: firmware: requesting b43/pcm5.fw [ 10.940552] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw [ 10.966269] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw [ 11.084276] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 11.104055] b43-phy0 debug: Chip initialized [ 11.104096] b43-phy0 debug: PIO initialized [ 11.104106] b43-phy0 debug: QoS disabled [ 11.124366] b43-phy0 debug: Wireless interface started [ 11.148853] b43-phy0 debug: Adding Interface type 2 [ 660.376274] b43-phy0 debug: Removing Interface type 2 [ 660.376359] b43-phy0 debug: Wireless interface stopped [ 667.296079] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 667.312082] b43-phy0 debug: Chip initialized [ 667.312122] b43-phy0 debug: PIO initialized [ 667.312132] b43-phy0 debug: QoS disabled [ 667.333144] b43-phy0 debug: Wireless interface started [ 667.356357] b43-phy0 debug: Adding Interface type 2 [ 667.472274] b43-phy0 debug: Removing Interface type 2 [ 667.472356] b43-phy0 debug: Wireless interface stopped [ 669.584280] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 669.600093] b43-phy0 debug: Chip initialized [ 669.600134] b43-phy0 debug: PIO initialized [ 669.600143] b43-phy0 debug: QoS disabled [ 669.620645] b43-phy0 debug: Wireless interface started [ 669.644096] b43-phy0 debug: Adding Interface type 2 and in /var/log/messages a lot of this messages: [ 1022.268919] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431 status=0 aid=1) [ 1022.268923] wlan0: associated [ 1022.269690] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local choice (reason=3) [ 1022.269826] cfg80211: Calling CRDA to update world regulatory domain [ 1023.600719] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) [ 1023.664562] wlan0: authenticated [ 1023.664687] wlan0: associate with 00:18:4d:2e:85:4a (try 1) [ 1023.864521] wlan0: associate with 00:18:4d:2e:85:4a (try 2) [ 1024.064534] wlan0: associate with 00:18:4d:2e:85:4a (try 3) [ 1024.264024] wlan0: association with 00:18:4d:2e:85:4a timed out [ 1034.841535] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) [ 1035.040024] wlan0: authenticate with 00:18:4d:2e:85:4a (try 2) [ 1035.240023] wlan0: authenticate with 00:18:4d:2e:85:4a (try 3) [ 1035.440035] wlan0: authentication with 00:18:4d:2e:85:4a timed out 2010/6/1 Martino Salvetti <the9ull@silix.org> > Also me... I sent a message about this problem but it was blocked. > > I have this problem olny with multi-AP networks, in dmesg I can see that it > continue to changes the AP until they ends to responds. (At my home, with a > digicom ADSL router, the wifi works) > > Martino > > 2010/6/1 William Bourque <william.bourque@polymtl.ca> > > >> Just saying, I have a similar problem... I tried to post twice about it >> on the list since 2 weeks but the mails keep getting moderated (and >> never unmoderated) because of "suspicious content". >> >> - William >> >> _______________________________________________ >> b43-dev mailing list >> b43-dev at lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/b43-dev >> > > > > -- > Remember: with great power comes great current squared times resistance. > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100620/fb5a8cac/attachment-0001.html> ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-20 12:04 ` Fabrizio Regalli @ 2010-06-20 18:12 ` Gábor Stefanik [not found] ` <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com> 0 siblings, 1 reply; 24+ messages in thread From: Gábor Stefanik @ 2010-06-20 18:12 UTC (permalink / raw) To: b43-dev On Sun, Jun 20, 2010 at 2:04 PM, Fabrizio Regalli <fabreg@gmail.com> wrote: > I'm trying with an oldest firmware revision but unfortunately, nothing > changed. > > debiancasa:/home/rizla# dmesg |grep b43 > [??? 2.054445] b43-pci-bridge 0000:04:05.0: PCI INT A -> GSI 17 (level, low) > -> IRQ 17 > [??? 8.338798] b43-phy0: Broadcom 4318 WLAN found (core revision 9) > [??? 8.380033] b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 > [??? 8.380054] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, > Revision 8 > [??? 8.577430] Registered led device: b43-phy0::tx > [??? 8.577443] Registered led device: b43-phy0::rx > [??? 8.577455] Registered led device: b43-phy0::assoc > [??? 8.577470] Registered led device: b43-phy0::radio > [?? 10.844287] b43 ssb0:0: firmware: requesting b43/ucode5.fw > [?? 10.924217] b43 ssb0:0: firmware: requesting b43/pcm5.fw > [?? 10.940552] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw > [?? 10.966269] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw > [?? 11.084276] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [?? 11.104055] b43-phy0 debug: Chip initialized > [?? 11.104096] b43-phy0 debug: PIO initialized Why are you using PIO for a BCM4318? AFAIK the DMA bug only affects BCM4312. > [?? 11.104106] b43-phy0 debug: QoS disabled > [?? 11.124366] b43-phy0 debug: Wireless interface started > [?? 11.148853] b43-phy0 debug: Adding Interface type 2 > [? 660.376274] b43-phy0 debug: Removing Interface type 2 > [? 660.376359] b43-phy0 debug: Wireless interface stopped > [? 667.296079] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [? 667.312082] b43-phy0 debug: Chip initialized > [? 667.312122] b43-phy0 debug: PIO initialized > [? 667.312132] b43-phy0 debug: QoS disabled > [? 667.333144] b43-phy0 debug: Wireless interface started > [? 667.356357] b43-phy0 debug: Adding Interface type 2 > [? 667.472274] b43-phy0 debug: Removing Interface type 2 > [? 667.472356] b43-phy0 debug: Wireless interface stopped > [? 669.584280] b43-phy0: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [? 669.600093] b43-phy0 debug: Chip initialized > [? 669.600134] b43-phy0 debug: PIO initialized > [? 669.600143] b43-phy0 debug: QoS disabled > [? 669.620645] b43-phy0 debug: Wireless interface started > [? 669.644096] b43-phy0 debug: Adding Interface type 2 > > and in /var/log/messages a lot of this messages: > > [ 1022.268919] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431 > status=0 aid=1) > [ 1022.268923] wlan0: associated > [ 1022.269690] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local > choice (reason=3) > [ 1022.269826] cfg80211: Calling CRDA to update world regulatory domain > [ 1023.600719] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) > [ 1023.664562] wlan0: authenticated > [ 1023.664687] wlan0: associate with 00:18:4d:2e:85:4a (try 1) > [ 1023.864521] wlan0: associate with 00:18:4d:2e:85:4a (try 2) > [ 1024.064534] wlan0: associate with 00:18:4d:2e:85:4a (try 3) > [ 1024.264024] wlan0: association with 00:18:4d:2e:85:4a timed out > [ 1034.841535] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) > [ 1035.040024] wlan0: authenticate with 00:18:4d:2e:85:4a (try 2) > [ 1035.240023] wlan0: authenticate with 00:18:4d:2e:85:4a (try 3) > [ 1035.440035] wlan0: authentication with 00:18:4d:2e:85:4a timed out > > > > > > 2010/6/1 Martino Salvetti <the9ull@silix.org> >> >> Also me... I sent a message about this problem but it was blocked. >> I have this problem olny with multi-AP networks, in dmesg I can see that >> it continue to changes the AP until they ends to responds. (At my home, with >> a digicom ADSL router, the wifi works) >> Martino >> >> 2010/6/1 William Bourque <william.bourque@polymtl.ca> >>> >>> Just saying, I have a similar problem... I tried to post twice about it >>> on the list since 2 weeks but the mails keep getting moderated (and >>> never unmoderated) because of "suspicious content". >>> >>> - William >>> >>> _______________________________________________ >>> b43-dev mailing list >>> b43-dev at lists.infradead.org >>> http://lists.infradead.org/mailman/listinfo/b43-dev >> >> >> >> -- >> Remember: with great power comes great current squared times resistance. >> >> _______________________________________________ >> b43-dev mailing list >> b43-dev at lists.infradead.org >> http://lists.infradead.org/mailman/listinfo/b43-dev >> > > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev > > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 24+ messages in thread
[parent not found: <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com>]
* Problem with b43 [not found] ` <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com> @ 2010-06-21 23:22 ` Gábor Stefanik 2010-06-22 15:09 ` Larry Finger 0 siblings, 1 reply; 24+ messages in thread From: Gábor Stefanik @ 2010-06-21 23:22 UTC (permalink / raw) To: b43-dev 2010/6/22 Fabrizio Regalli <fabreg@gmail.com>: > 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. (BTW, please always CC the list / use Reply to All. Otherwise others on the list can't follow this thread.) > Thanks again. > > > 2010/6/20 G?bor Stefanik <netrolller.3d@gmail.com> >> >> On Sun, Jun 20, 2010 at 2:04 PM, Fabrizio Regalli <fabreg@gmail.com> >> wrote: >> > I'm trying with an oldest firmware revision but unfortunately, nothing >> > changed. >> > >> > debiancasa:/home/rizla# dmesg |grep b43 >> > [??? 2.054445] b43-pci-bridge 0000:04:05.0: PCI INT A -> GSI 17 (level, >> > low) >> > -> IRQ 17 >> > [??? 8.338798] b43-phy0: Broadcom 4318 WLAN found (core revision 9) >> > [??? 8.380033] b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 >> > [??? 8.380054] b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, >> > Revision 8 >> > [??? 8.577430] Registered led device: b43-phy0::tx >> > [??? 8.577443] Registered led device: b43-phy0::rx >> > [??? 8.577455] Registered led device: b43-phy0::assoc >> > [??? 8.577470] Registered led device: b43-phy0::radio >> > [?? 10.844287] b43 ssb0:0: firmware: requesting b43/ucode5.fw >> > [?? 10.924217] b43 ssb0:0: firmware: requesting b43/pcm5.fw >> > [?? 10.940552] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw >> > [?? 10.966269] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw >> > [?? 11.084276] b43-phy0: Loading firmware version 410.2160 (2007-05-26 >> > 15:32:10) >> > [?? 11.104055] b43-phy0 debug: Chip initialized >> > [?? 11.104096] b43-phy0 debug: PIO initialized >> >> Why are you using PIO for a BCM4318? AFAIK the DMA bug only affects >> BCM4312. >> >> > [?? 11.104106] b43-phy0 debug: QoS disabled >> > [?? 11.124366] b43-phy0 debug: Wireless interface started >> > [?? 11.148853] b43-phy0 debug: Adding Interface type 2 >> > [? 660.376274] b43-phy0 debug: Removing Interface type 2 >> > [? 660.376359] b43-phy0 debug: Wireless interface stopped >> > [? 667.296079] b43-phy0: Loading firmware version 410.2160 (2007-05-26 >> > 15:32:10) >> > [? 667.312082] b43-phy0 debug: Chip initialized >> > [? 667.312122] b43-phy0 debug: PIO initialized >> > [? 667.312132] b43-phy0 debug: QoS disabled >> > [? 667.333144] b43-phy0 debug: Wireless interface started >> > [? 667.356357] b43-phy0 debug: Adding Interface type 2 >> > [? 667.472274] b43-phy0 debug: Removing Interface type 2 >> > [? 667.472356] b43-phy0 debug: Wireless interface stopped >> > [? 669.584280] b43-phy0: Loading firmware version 410.2160 (2007-05-26 >> > 15:32:10) >> > [? 669.600093] b43-phy0 debug: Chip initialized >> > [? 669.600134] b43-phy0 debug: PIO initialized >> > [? 669.600143] b43-phy0 debug: QoS disabled >> > [? 669.620645] b43-phy0 debug: Wireless interface started >> > [? 669.644096] b43-phy0 debug: Adding Interface type 2 >> > >> > and in /var/log/messages a lot of this messages: >> > >> > [ 1022.268919] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x431 >> > status=0 aid=1) >> > [ 1022.268923] wlan0: associated >> > [ 1022.269690] wlan0: deauthenticating from 00:18:4d:2e:85:4a by local >> > choice (reason=3) >> > [ 1022.269826] cfg80211: Calling CRDA to update world regulatory domain >> > [ 1023.600719] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) >> > [ 1023.664562] wlan0: authenticated >> > [ 1023.664687] wlan0: associate with 00:18:4d:2e:85:4a (try 1) >> > [ 1023.864521] wlan0: associate with 00:18:4d:2e:85:4a (try 2) >> > [ 1024.064534] wlan0: associate with 00:18:4d:2e:85:4a (try 3) >> > [ 1024.264024] wlan0: association with 00:18:4d:2e:85:4a timed out >> > [ 1034.841535] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) >> > [ 1035.040024] wlan0: authenticate with 00:18:4d:2e:85:4a (try 2) >> > [ 1035.240023] wlan0: authenticate with 00:18:4d:2e:85:4a (try 3) >> > [ 1035.440035] wlan0: authentication with 00:18:4d:2e:85:4a timed out >> > >> > >> > >> > >> > >> > 2010/6/1 Martino Salvetti <the9ull@silix.org> >> >> >> >> Also me... I sent a message about this problem but it was blocked. >> >> I have this problem olny with multi-AP networks, in dmesg I can see >> >> that >> >> it continue to changes the AP until they ends to responds. (At my home, >> >> with >> >> a digicom ADSL router, the wifi works) >> >> Martino >> >> >> >> 2010/6/1 William Bourque <william.bourque@polymtl.ca> >> >>> >> >>> Just saying, I have a similar problem... I tried to post twice about >> >>> it >> >>> on the list since 2 weeks but the mails keep getting moderated (and >> >>> never unmoderated) because of "suspicious content". >> >>> >> >>> - William >> >>> >> >>> _______________________________________________ >> >>> b43-dev mailing list >> >>> b43-dev at lists.infradead.org >> >>> http://lists.infradead.org/mailman/listinfo/b43-dev >> >> >> >> >> >> >> >> -- >> >> Remember: with great power comes great current squared times >> >> resistance. >> >> >> >> _______________________________________________ >> >> b43-dev mailing list >> >> b43-dev at lists.infradead.org >> >> http://lists.infradead.org/mailman/listinfo/b43-dev >> >> >> > >> > >> > _______________________________________________ >> > b43-dev mailing list >> > b43-dev at lists.infradead.org >> > http://lists.infradead.org/mailman/listinfo/b43-dev >> > >> > >> >> >> >> -- >> Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) > > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-21 23:22 ` Gábor Stefanik @ 2010-06-22 15:09 ` Larry Finger 2010-06-22 18:54 ` Fabrizio Regalli 0 siblings, 1 reply; 24+ messages in thread From: Larry Finger @ 2010-06-22 15:09 UTC (permalink / raw) To: b43-dev On 06/21/2010 06:22 PM, G?bor Stefanik wrote: > 2010/6/22 Fabrizio Regalli <fabreg@gmail.com>: >> 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 ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-22 15:09 ` Larry Finger @ 2010-06-22 18:54 ` Fabrizio Regalli 2010-06-22 19:46 ` Larry Finger 0 siblings, 1 reply; 24+ messages in thread From: Fabrizio Regalli @ 2010-06-22 18:54 UTC (permalink / raw) To: b43-dev 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. ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-22 18:54 ` Fabrizio Regalli @ 2010-06-22 19:46 ` Larry Finger 2010-06-22 20:40 ` Fabrizio Regalli 0 siblings, 1 reply; 24+ messages in thread From: Larry Finger @ 2010-06-22 19:46 UTC (permalink / raw) To: b43-dev On 06/22/2010 01:54 PM, Fabrizio Regalli wrote: > 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 That step was not necessary. I run under the KDE NetworkManager all the time. > 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 Yes, you are associated. > > ## 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) You also have an IP number. Some systems have trouble with IPv6. If you do not need it, you might disable it. > 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 <http://192.168.0.2>: icmp_req=1 ttl=64 > time=2180 ms > 64 bytes from 192.168.0.2 <http://192.168.0.2>: icmp_req=3 ttl=64 > time=888 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 Yes - awful performance. > > .. > > I'm using wpa_supplicant with wpa2 authentication Could be this the > problem? No. I use WPA2 authentication all the time. I have no idea what is causing the changes in performance. I do not see them. My system will go off-line once in a while, but I never see the dropouts or the very long ping times. Larry ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-22 19:46 ` Larry Finger @ 2010-06-22 20:40 ` Fabrizio Regalli 2010-06-24 21:50 ` Fabrizio Regalli 0 siblings, 1 reply; 24+ messages in thread From: Fabrizio Regalli @ 2010-06-22 20:40 UTC (permalink / raw) To: b43-dev Now I switched to WEP auth, for trying: wlan0 IEEE 802.11bg ESSID:"XXXX" Mode:Managed Frequency:2.437 GHz Access Point: 00:18:4D:2E:85:4A Bit Rate=5.5 Mb/s Tx-Power=20 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX Power Management:off Link Quality=70/70 Signal level=-23 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 The wlan0 interface is up & running: ifconfig wlan0 |grep inet 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 but nothing to do: it does not ping the ap (192.168.0.2) PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. --- 192.168.0.2 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2016ms Here's a dmesg output: [ 160.482533] b43-phy1: Broadcom 4318 WLAN found (core revision 9) [ 160.524036] b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7 [ 160.524058] b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 [ 160.548601] phy1: Selected rate control algorithm 'minstrel' [ 160.549717] Registered led device: b43-phy1::tx [ 160.549746] Registered led device: b43-phy1::rx [ 160.549778] Registered led device: b43-phy1::assoc [ 160.549799] Registered led device: b43-phy1::radio [ 160.549911] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ] [ 181.508303] b43 ssb0:0: firmware: requesting b43/ucode5.fw [ 181.510885] b43 ssb0:0: firmware: requesting b43/pcm5.fw [ 181.513857] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw [ 181.516679] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw [ 181.632028] b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 181.652056] b43-phy1 debug: Chip initialized [ 181.652203] b43-phy1 debug: 32-bit DMA initialized [ 181.652211] b43-phy1 debug: QoS disabled [ 181.672368] b43-phy1 debug: Wireless interface started [ 181.704094] b43-phy1 debug: Adding Interface type 2 [ 181.734463] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 181.916349] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) [ 181.917759] wlan0: 00:18:4d:2e:85:4a denied authentication (status 13) [ 181.918140] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) [ 181.923714] wlan0: authenticated [ 181.924100] wlan0: associate with 00:18:4d:2e:85:4a (try 1) [ 181.925832] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x411 status=0 aid=1) [ 181.925834] wlan0: associated [ 181.926327] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 191.932006] wlan0: no IPv6 routers present I'm using a netgear WG602 v3 as access point with 1.2.5 firmware. Now I'm trying to upgrade AP firmware with WRT 2010/6/22 Larry Finger <Larry.Finger@lwfinger.net> > On 06/22/2010 01:54 PM, Fabrizio Regalli wrote: > > 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 > > That step was not necessary. I run under the KDE NetworkManager all the > time. > > > 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 > > Yes, you are associated. > > > > > ## 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) > > You also have an IP number. Some systems have trouble with IPv6. If you do > not need it, you might disable it. > > > 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 <http://192.168.0.2>: icmp_req=1 ttl=64 > > time=2180 ms > > 64 bytes from 192.168.0.2 <http://192.168.0.2>: icmp_req=3 ttl=64 > > time=888 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 > > Yes - awful performance. > > > > > .. > > > > I'm using wpa_supplicant with wpa2 authentication Could be this the > > problem? > > No. I use WPA2 authentication all the time. > > I have no idea what is causing the changes in performance. I do not see > them. My system will go off-line once in a while, but I never see the > dropouts or the very long ping times. > > Larry > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100622/baa5d1c7/attachment.html> ^ permalink raw reply [flat|nested] 24+ messages in thread
* Problem with b43 2010-06-22 20:40 ` Fabrizio Regalli @ 2010-06-24 21:50 ` Fabrizio Regalli 0 siblings, 0 replies; 24+ messages in thread From: Fabrizio Regalli @ 2010-06-24 21:50 UTC (permalink / raw) To: b43-dev Hello, I've update WRT on my netgear router without success: the problem is not solved So I've changed the access point with another netgear and now works fine. The only "strange" message is [ 1558.692139] b43-phy0 ERROR: PHY transmission error what does it means? Thanks 2010/6/22 Fabrizio Regalli <fabreg@gmail.com> > Now I switched to WEP auth, for trying: > > > > wlan0 IEEE 802.11bg ESSID:"XXXX" > Mode:Managed Frequency:2.437 GHz Access Point: > 00:18:4D:2E:85:4A > Bit Rate=5.5 Mb/s Tx-Power=20 dBm > Retry long limit:7 RTS thr:off Fragment thr:off > Encryption key:XXXX-XXXX-XXXX-XXXX-XXXX-XXXX > Power Management:off > Link Quality=70/70 Signal level=-23 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > The wlan0 interface is up & running: > > ifconfig wlan0 |grep inet > > 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 > > but nothing to do: it does not ping the ap (192.168.0.2) > > PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data. > > > --- 192.168.0.2 ping statistics --- > 3 packets transmitted, 0 received, 100% packet loss, time 2016ms > > Here's a dmesg output: > > [ 160.482533] b43-phy1: Broadcom 4318 WLAN found (core revision 9) > [ 160.524036] b43-phy1 debug: Found PHY: Analog 3, Type 2, Revision 7 > [ 160.524058] b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, > Revision 8 > [ 160.548601] phy1: Selected rate control algorithm 'minstrel' > [ 160.549717] Registered led device: b43-phy1::tx > [ 160.549746] Registered led device: b43-phy1::rx > [ 160.549778] Registered led device: b43-phy1::assoc > [ 160.549799] Registered led device: b43-phy1::radio > [ 160.549911] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: > FW13 ] > [ 181.508303] b43 ssb0:0: firmware: requesting b43/ucode5.fw > [ 181.510885] b43 ssb0:0: firmware: requesting b43/pcm5.fw > [ 181.513857] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw > [ 181.516679] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw > [ 181.632028] b43-phy1: Loading firmware version 410.2160 (2007-05-26 > 15:32:10) > [ 181.652056] b43-phy1 debug: Chip initialized > [ 181.652203] b43-phy1 debug: 32-bit DMA initialized > [ 181.652211] b43-phy1 debug: QoS disabled > [ 181.672368] b43-phy1 debug: Wireless interface started > [ 181.704094] b43-phy1 debug: Adding Interface type 2 > [ 181.734463] ADDRCONF(NETDEV_UP): wlan0: link is not ready > [ 181.916349] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) > [ 181.917759] wlan0: 00:18:4d:2e:85:4a denied authentication (status 13) > [ 181.918140] wlan0: authenticate with 00:18:4d:2e:85:4a (try 1) > [ 181.923714] wlan0: authenticated > [ 181.924100] wlan0: associate with 00:18:4d:2e:85:4a (try 1) > [ 181.925832] wlan0: RX AssocResp from 00:18:4d:2e:85:4a (capab=0x411 > status=0 aid=1) > [ 181.925834] wlan0: associated > [ 181.926327] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > [ 191.932006] wlan0: no IPv6 routers present > > I'm using a netgear WG602 v3 as access point with 1.2.5 firmware. > > Now I'm trying to upgrade AP firmware with WRT > > > 2010/6/22 Larry Finger <Larry.Finger@lwfinger.net> > >> On 06/22/2010 01:54 PM, Fabrizio Regalli wrote: >> >> > 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 >> >> That step was not necessary. I run under the KDE NetworkManager all the >> time. >> >> > 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 >> >> Yes, you are associated. >> >> > >> > ## 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) >> >> You also have an IP number. Some systems have trouble with IPv6. If you do >> not need it, you might disable it. >> >> > 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 <http://192.168.0.2>: icmp_req=1 ttl=64 >> > time=2180 ms >> > 64 bytes from 192.168.0.2 <http://192.168.0.2>: icmp_req=3 ttl=64 >> > time=888 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 >> >> Yes - awful performance. >> >> > >> > .. >> > >> > I'm using wpa_supplicant with wpa2 authentication Could be this the >> > problem? >> >> No. I use WPA2 authentication all the time. >> >> I have no idea what is causing the changes in performance. I do not see >> them. My system will go off-line once in a while, but I never see the >> dropouts or the very long ping times. >> >> Larry >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20100624/37c71f48/attachment.html> ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 @ 2010-09-24 16:55 Cyrille 2010-09-24 17:06 ` Gábor Stefanik 2010-09-24 17:10 ` Rafał Miłecki 0 siblings, 2 replies; 24+ messages in thread From: Cyrille @ 2010-09-24 16:55 UTC (permalink / raw) To: b43-dev Hi I've got a problem with a broadcom 4312 [12e4:4315]. The environment : =========================== uname -a 2.6.35.5-libre.29.fc14.x86_64 lspci -vnn 0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at fe7fc000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 <?> Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 7f-78-4e-ff-ff-6d-00-23 Capabilities: [16c] Power Budgeting <?> Kernel driver in use: b43-pci-bridge Kernel modules: ssb =============================== Installation method ( http://wireless.kernel.org/en/users/Drivers/b43#fw-b43-lp ) : You are using the b43 driver from linux-2.6.25 or newer export FIRMWARE_INSTALL_DIR="/lib/firmware" wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 tar xjf broadcom-wl-4.150.10.5.tar.bz2 cd broadcom-wl-4.150.10.5/driver sudo ../../b43-fwcutter-013/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta_mimo.o Seems work : ls /lib/firmware/b43-open/ a0g0bsinitvals5.fw a0g1bsinitvals9.fw b0g0bsinitvals9.fw lp0bsinitvals15.fw n0initvals11.fw ucode5.fw a0g0bsinitvals9.fw a0g1initvals13.fw b0g0initvals13.fw lp0initvals13.fw pcm5.fw ucode9.fw a0g0initvals5.fw a0g1initvals5.fw b0g0initvals5.fw lp0initvals14.fw ucode11.fw a0g0initvals9.fw a0g1initvals9.fw b0g0initvals9.fw lp0initvals15.fw ucode13.fw a0g1bsinitvals13.fw b0g0bsinitvals13.fw lp0bsinitvals13.fw n0absinitvals11.fw ucode14.fw a0g1bsinitvals5.fw b0g0bsinitvals5.fw lp0bsinitvals14.fw n0bsinitvals11.fw ucode15.fw But : dmesg b43-phy3 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. b43-phy4: Broadcom 4312 WLAN found (core revision 15) b43-phy4 debug: Found PHY: Analog 6, Type 5, Revision 1 b43-phy4 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 phy4: Selected rate control algorithm 'minstrel' Registered led device: b43-phy4::tx Registered led device: b43-phy4::rx Registered led device: b43-phy4::radio Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] ssb0:0: Missing Free firmware b43-phy4 ERROR: Rejected non-Free firmware ssb0:0: Missing Free firmware b43-phy4 ERROR: Rejected non-Free firmware So don't work. Grrrrrrrrrrrrrrrrrrrr I thought nevertheless that with this kernel that was going to work. No idea, I thing is due of the model [12e4:4315]. Is there anyone who can say to me if it possible to install and configure this card with a free-kernel. Thanx ! Cyrille ---- [ cyrille at cbiot.fr | http://cbiot.fr ] "Et le combat cessa faute de combattants." --- Le Cid (1636), IV, 3, Rodrigue - - - - BLAG : http://blagblagblag.org Blag'em up! http://zenblagger.org ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 16:55 problem " Cyrille @ 2010-09-24 17:06 ` Gábor Stefanik 2010-09-24 17:21 ` John W. Linville 2010-09-24 17:10 ` Rafał Miłecki 1 sibling, 1 reply; 24+ messages in thread From: Gábor Stefanik @ 2010-09-24 17:06 UTC (permalink / raw) To: Cyrille; +Cc: b43-dev, John Linville, linux-wireless On Fri, Sep 24, 2010 at 6:55 PM, Cyrille <cyrille@cbiot.fr> wrote: > Hi > I've got a problem with a broadcom 4312 [12e4:4315]. > The environment : > =========================== > uname -a > 2.6.35.5-libre.29.fc14.x86_64 > > lspci -vnn > 0b:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g [14e4:4315] (rev 01) > ? ? ? ?Subsystem: Dell Wireless 1395 WLAN Mini-Card [1028:000b] > ? ? ? ?Flags: bus master, fast devsel, latency 0, IRQ 17 > ? ? ? ?Memory at fe7fc000 (64-bit, non-prefetchable) [size=16K] > ? ? ? ?Capabilities: [40] Power Management version 3 > ? ? ? ?Capabilities: [58] Vendor Specific Information: Len=78 <?> > ? ? ? ?Capabilities: [e8] MSI: Enable- Count=1/1 Maskable- 64bit+ > ? ? ? ?Capabilities: [d0] Express Endpoint, MSI 00 > ? ? ? ?Capabilities: [100] Advanced Error Reporting > ? ? ? ?Capabilities: [13c] Virtual Channel > ? ? ? ?Capabilities: [160] Device Serial Number 7f-78-4e-ff-ff-6d-00-23 > ? ? ? ?Capabilities: [16c] Power Budgeting <?> > ? ? ? ?Kernel driver in use: b43-pci-bridge > ? ? ? ?Kernel modules: ssb > =============================== > > Installation method ( http://wireless.kernel.org/en/users/Drivers/b43#fw-b43-lp ) : > You are using the b43 driver from linux-2.6.25 or newer > export FIRMWARE_INSTALL_DIR="/lib/firmware" > wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 > tar xjf broadcom-wl-4.150.10.5.tar.bz2 > cd broadcom-wl-4.150.10.5/driver > sudo ../../b43-fwcutter-013/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta_mimo.o You are using the firmware for G-PHYs. Yo should use v4.174 (also known as v4.178) for LP-PHY. > > > Seems work : ls /lib/firmware/b43-open/ > a0g0bsinitvals5.fw ? a0g1bsinitvals9.fw ? b0g0bsinitvals9.fw ?lp0bsinitvals15.fw ?n0initvals11.fw ?ucode5.fw > a0g0bsinitvals9.fw ? a0g1initvals13.fw ? ?b0g0initvals13.fw ? lp0initvals13.fw ? ?pcm5.fw ? ? ? ? ?ucode9.fw > a0g0initvals5.fw ? ? a0g1initvals5.fw ? ? b0g0initvals5.fw ? ?lp0initvals14.fw ? ?ucode11.fw > a0g0initvals9.fw ? ? a0g1initvals9.fw ? ? b0g0initvals9.fw ? ?lp0initvals15.fw ? ?ucode13.fw > a0g1bsinitvals13.fw ?b0g0bsinitvals13.fw ?lp0bsinitvals13.fw ?n0absinitvals11.fw ?ucode14.fw > a0g1bsinitvals5.fw ? b0g0bsinitvals5.fw ? lp0bsinitvals14.fw ?n0bsinitvals11.fw ? ucode15.fw Extract to /lib/firmware/b43. /lib/firmware/b43-open is only for OpenFWWF. > > > But : > dmesg > b43-phy3 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. > b43-phy4: Broadcom 4312 WLAN found (core revision 15) > b43-phy4 debug: Found PHY: Analog 6, Type 5, Revision 1 > b43-phy4 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 > phy4: Selected rate control algorithm 'minstrel' > Registered led device: b43-phy4::tx > Registered led device: b43-phy4::rx > Registered led device: b43-phy4::radio > Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] > ssb0:0: Missing Free firmware > b43-phy4 ERROR: Rejected non-Free firmware > ssb0:0: Missing Free firmware > b43-phy4 ERROR: Rejected non-Free firmware Compile compat-wireless to bypass the "free-only" patch in Fedora. (John, are you still maintaining the Fedora kernel's wireless part? If so, please kill this "freedom enforcement"!) > > > So don't work. > Grrrrrrrrrrrrrrrrrrrr > I thought nevertheless that with this kernel that was going to work. > No idea, I thing is due of the model [12e4:4315]. Is there anyone who can say to me if it possible to install and configure this card with a free-kernel. > > Thanx ! > > Cyrille > > > > ---- > [ cyrille at cbiot.fr | http://cbiot.fr ] > > "Et le combat cessa faute de combattants." > --- Le Cid (1636), IV, 3, Rodrigue - - - - > > BLAG : http://blagblagblag.org > Blag'em up! http://zenblagger.org > > > > _______________________________________________ > b43-dev mailing list > b43-dev at lists.infradead.org > http://lists.infradead.org/mailman/listinfo/b43-dev > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:06 ` Gábor Stefanik @ 2010-09-24 17:21 ` John W. Linville 2010-09-24 17:30 ` Gábor Stefanik 2010-09-24 17:39 ` Cyrille 0 siblings, 2 replies; 24+ messages in thread From: John W. Linville @ 2010-09-24 17:21 UTC (permalink / raw) To: Gábor Stefanik; +Cc: Cyrille, b43-dev, linux-wireless On Fri, Sep 24, 2010 at 07:06:17PM +0200, G?bor Stefanik wrote: > On Fri, Sep 24, 2010 at 6:55 PM, Cyrille <cyrille@cbiot.fr> wrote: > > Hi > > I've got a problem with a broadcom 4312 [12e4:4315]. > > The environment : > > =========================== > > uname -a > > 2.6.35.5-libre.29.fc14.x86_64 > > Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] > > ssb0:0: Missing Free firmware > > b43-phy4 ERROR: Rejected non-Free firmware > > ssb0:0: Missing Free firmware > > b43-phy4 ERROR: Rejected non-Free firmware > > Compile compat-wireless to bypass the "free-only" patch in Fedora. > > (John, are you still maintaining the Fedora kernel's wireless part? If > so, please kill this "freedom enforcement"!) This isn't a Fedora kernel. I'm guessing it is from "Free-dora" by way of BLAG, and I have no control over it -- sorry. Cyrille, did you try b43-openfwwf? If that doesn't work, then you will need to use extracted proprietary firmware with some other kernel (e.g. stock Fedora) or you will have to live without b43. John -- John W. Linville Someday the world will need a hero, and you linville at tuxdriver.com might be all we have. Be ready. ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:21 ` John W. Linville @ 2010-09-24 17:30 ` Gábor Stefanik 2010-09-24 17:43 ` Michael Büsch 2010-09-24 17:39 ` Cyrille 1 sibling, 1 reply; 24+ messages in thread From: Gábor Stefanik @ 2010-09-24 17:30 UTC (permalink / raw) To: John W. Linville; +Cc: Cyrille, b43-dev, linux-wireless 2010/9/24 John W. Linville <linville@tuxdriver.com>: > On Fri, Sep 24, 2010 at 07:06:17PM +0200, G?bor Stefanik wrote: >> On Fri, Sep 24, 2010 at 6:55 PM, Cyrille <cyrille@cbiot.fr> wrote: >> > Hi >> > I've got a problem with a broadcom 4312 [12e4:4315]. >> > The environment : >> > =========================== >> > uname -a >> > 2.6.35.5-libre.29.fc14.x86_64 > >> > Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] >> > ssb0:0: Missing Free firmware >> > b43-phy4 ERROR: Rejected non-Free firmware >> > ssb0:0: Missing Free firmware >> > b43-phy4 ERROR: Rejected non-Free firmware >> >> Compile compat-wireless to bypass the "free-only" patch in Fedora. >> >> (John, are you still maintaining the Fedora kernel's wireless part? If >> so, please kill this "freedom enforcement"!) > > This isn't a Fedora kernel. ?I'm guessing it is from "Free-dora" > by way of BLAG, and I have no control over it -- sorry. > > Cyrille, did you try b43-openfwwf? ?If that doesn't work, then you > will need to use extracted proprietary firmware with some other kernel > (e.g. stock Fedora) or you will have to live without b43. OpenFWWF definitely won't work with LP-PHYs. We don't even know enough about LP-PHY to fix the DMA error, let alone to write our own firmware... > > John > -- > John W. Linville ? ? ? ? ? ? ? ?Someday the world will need a hero, and you > linville at tuxdriver.com ? ? ? ? ? ? ? ? ?might be all we have. ?Be ready. > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:30 ` Gábor Stefanik @ 2010-09-24 17:43 ` Michael Büsch 0 siblings, 0 replies; 24+ messages in thread From: Michael Büsch @ 2010-09-24 17:43 UTC (permalink / raw) To: Gábor Stefanik; +Cc: John W. Linville, linux-wireless, b43-dev On Fri, 2010-09-24 at 19:30 +0200, G?bor Stefanik wrote: > OpenFWWF definitely won't work with LP-PHYs. We don't even know enough > about LP-PHY to fix the DMA error, let alone to write our own > firmware... Well, the firmware is pretty much independent of the PHY that is used (except for some workarounds and some minor stuff). The firmware does only depend on the wireless MAC core revision. What 80211 core rev do LP PHY devices typically have? -- Greetings Michael. ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:21 ` John W. Linville 2010-09-24 17:30 ` Gábor Stefanik @ 2010-09-24 17:39 ` Cyrille 1 sibling, 0 replies; 24+ messages in thread From: Cyrille @ 2010-09-24 17:39 UTC (permalink / raw) To: John W. Linville; +Cc: Gábor Stefanik, b43-dev, linux-wireless > 'm guessing it is from "Free-dora" > by way of BLAG, and I have no control over it -- sorry. Yes I'm using a BLAG 119K with a free-dora kernel. Cyrille ---- [ cyrille at cbiot.fr | http://cbiot.fr ] "Et le combat cessa faute de combattants." --- Le Cid (1636), IV, 3, Rodrigue - - - - BLAG : http://blagblagblag.org Blag'em up! http://zenblagger.org ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 16:55 problem " Cyrille 2010-09-24 17:06 ` Gábor Stefanik @ 2010-09-24 17:10 ` Rafał Miłecki [not found] ` <20100924191547.59c58e7b.cyrille@cbiot.fr> 1 sibling, 1 reply; 24+ messages in thread From: Rafał Miłecki @ 2010-09-24 17:10 UTC (permalink / raw) To: b43-dev 2010/9/24 Cyrille <cyrille@cbiot.fr>: > Installation method ( http://wireless.kernel.org/en/users/Drivers/b43#fw-b43-lp ) : > You are using the b43 driver from linux-2.6.25 or newer > export FIRMWARE_INSTALL_DIR="/lib/firmware" > wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 > tar xjf broadcom-wl-4.150.10.5.tar.bz2 > cd broadcom-wl-4.150.10.5/driver > sudo ../../b43-fwcutter-013/b43-fwcutter -w "$FIRMWARE_INSTALL_DIR" wl_apsta_mimo.o This should lead to system having firmware in /lib/firmware/b43/. Make sure you have "some" files in this directory. > Seems work : ls /lib/firmware/b43-open/ > a0g0bsinitvals5.fw ? a0g1bsinitvals9.fw ? b0g0bsinitvals9.fw ?lp0bsinitvals15.fw ?n0initvals11.fw ?ucode5.fw > a0g0bsinitvals9.fw ? a0g1initvals13.fw ? ?b0g0initvals13.fw ? lp0initvals13.fw ? ?pcm5.fw ? ? ? ? ?ucode9.fw > a0g0initvals5.fw ? ? a0g1initvals5.fw ? ? b0g0initvals5.fw ? ?lp0initvals14.fw ? ?ucode11.fw > a0g0initvals9.fw ? ? a0g1initvals9.fw ? ? b0g0initvals9.fw ? ?lp0initvals15.fw ? ?ucode13.fw > a0g1bsinitvals13.fw ?b0g0bsinitvals13.fw ?lp0bsinitvals13.fw ?n0absinitvals11.fw ?ucode14.fw > a0g1bsinitvals5.fw ? b0g0bsinitvals5.fw ? lp0bsinitvals14.fw ?n0bsinitvals11.fw ? ucode15.fw b43-open is for open firmware, which does not support LP-PHY. You've to use original, closed source, ugly-licensed firmware (placed in /lib/firmware/b43/). > But : > dmesg > b43-phy3 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website. > b43-phy4: Broadcom 4312 WLAN found (core revision 15) > b43-phy4 debug: Found PHY: Analog 6, Type 5, Revision 1 > b43-phy4 debug: Found Radio: Manuf 0x17F, Version 0x2062, Revision 2 > phy4: Selected rate control algorithm 'minstrel' > Registered led device: b43-phy4::tx > Registered led device: b43-phy4::rx > Registered led device: b43-phy4::radio > Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ] > ssb0:0: Missing Free firmware > b43-phy4 ERROR: Rejected non-Free firmware > ssb0:0: Missing Free firmware > b43-phy4 ERROR: Rejected non-Free firmware Your distro doesn't allow non-free firmware. As I said, LP-PHY won't work with open firmware. Refer to your's distro FAQ/forums/MLs to learn how you can enable non-free firmware usage. -- Rafa? ^ permalink raw reply [flat|nested] 24+ messages in thread
[parent not found: <20100924191547.59c58e7b.cyrille@cbiot.fr>]
* problem with b43 [not found] ` <20100924191547.59c58e7b.cyrille@cbiot.fr> @ 2010-09-24 17:28 ` Rafał Miłecki 2010-09-24 17:32 ` Cyrille 0 siblings, 1 reply; 24+ messages in thread From: Rafał Miłecki @ 2010-09-24 17:28 UTC (permalink / raw) To: b43-dev W dniu 24 wrze?nia 2010 19:15 u?ytkownik Cyrille <cyrille@cbiot.fr> napisa?: >> Your distro doesn't allow non-free firmware. As I said, LP-PHY won't >> work with open firmware. Refer to your's distro FAQ/forums/MLs to >> learn how you can enable non-free firmware usage. > > OK That is clear.... > If to run this card I must use closed code, I don't want to use it and I don't looking for configure this card ! I'll wait an open solution > So I keep my netgear WG111v3 to wireless. > Thx to all. OpenFWWF (http://www.ing.unibs.it/openfwwf/) doesn't seem to be too active, don't expect too much in near future. You can help of course. Your's NETGEAR seems to be RTL818x chip based USB dongle. Are you sure it uses open source firmware? Yeah, it's firmware is probably embedded in device's internal memory... but it is still there. I'm afraid you won't be able to get it's sources. P.S. Please, use "Reply to all" button, to include ML as well in your's response. -- Rafa? ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:28 ` Rafał Miłecki @ 2010-09-24 17:32 ` Cyrille 2010-09-24 17:46 ` Rafał Miłecki 0 siblings, 1 reply; 24+ messages in thread From: Cyrille @ 2010-09-24 17:32 UTC (permalink / raw) To: b43-dev > Your's NETGEAR seems to be RTL818x chip based USB dongle. Are you sure > it uses open source firmware? Yeah, it's firmware is probably embedded > in device's internal memory... but it is still there. I'm afraid you > won't be able to get it's sources. This neatgears --> works out of the box with simply a free kernel. Severals Blaggers use it (trisqueland gnewsense too ) Thx ! ---- [ cyrille at cbiot.fr | http://cbiot.fr ] "Et le combat cessa faute de combattants." --- Le Cid (1636), IV, 3, Rodrigue - - - - BLAG : http://blagblagblag.org Blag'em up! http://zenblagger.org ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:32 ` Cyrille @ 2010-09-24 17:46 ` Rafał Miłecki 2010-09-24 18:32 ` Cyrille 0 siblings, 1 reply; 24+ messages in thread From: Rafał Miłecki @ 2010-09-24 17:46 UTC (permalink / raw) To: b43-dev W dniu 24 wrze?nia 2010 19:32 u?ytkownik Cyrille <cyrille@cbiot.fr> napisa?: >> Your's NETGEAR seems to be RTL818x chip based USB dongle. Are you sure >> it uses open source firmware? Yeah, it's firmware is probably embedded >> in device's internal memory... but it is still there. I'm afraid you >> won't be able to get it's sources. > > This neatgears --> works out of the box with simply a free kernel. Severals Blaggers use it (trisqueland gnewsense too ) Please, Google/Wiki for "firmware". * Both chipsets need firmware * Both firmwares are not open sourced * Both firmwares are executed on device (not on your machine) RTL818X card has firmware embedded on device. Broadcom needs system to send firmware to card. Not much difference for me. Of course you may still like RTL much more that Broadcom, just wanted to make sure you understand situation. -- Rafa? ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 17:46 ` Rafał Miłecki @ 2010-09-24 18:32 ` Cyrille 2010-09-24 18:39 ` Peter Stuge 0 siblings, 1 reply; 24+ messages in thread From: Cyrille @ 2010-09-24 18:32 UTC (permalink / raw) To: b43-dev > Not much difference for me. Of course you may still like RTL much more > that Broadcom, just wanted to make sure you understand situation. Don't really understand, before buy the neatgear, I post on different forum or IRC and everybody seems say that this model was recommended by fsf ( http://www.fsf.org/resources/hw/index_html/net/wireless/index_html/cards.html ) Is it used free "technology" or not ? It is very complicated for French to understand all these subtleties! ---- [ cyrille at cbiot.fr | http://cbiot.fr ] "Et le combat cessa faute de combattants." --- Le Cid (1636), IV, 3, Rodrigue - - - - BLAG : http://blagblagblag.org Blag'em up! http://zenblagger.org ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 18:32 ` Cyrille @ 2010-09-24 18:39 ` Peter Stuge 2010-09-24 19:28 ` Nicolas de Pesloüan 0 siblings, 1 reply; 24+ messages in thread From: Peter Stuge @ 2010-09-24 18:39 UTC (permalink / raw) To: b43-dev Cyrille wrote: > Don't really understand, before buy the neatgear, I post on > different forum or IRC and everybody seems say that this model was > recommended by fsf ( http://www.fsf.org/resources/hw/index_html/net/wireless/index_html/cards.html ) > Is it used free "technology" or not ? It depends on your definition. There is software inside almost every device which is not free. There is a small computer inside every hard drive, every networking card, every wifi card, every part of a computer. If that software must be open and available then no device is free. If it is OK to consider the device as a hardware (also when a part of it is non-free software) and the hardware being free as long as it can be *used* with free software, then very many devices are free, including b43 wireless cards using non-free software inside the device. > It is very complicated for French to understand all these subtleties! Maybe you can find a technical group in your area which can explain it in your language. //Peter ^ permalink raw reply [flat|nested] 24+ messages in thread
* problem with b43 2010-09-24 18:39 ` Peter Stuge @ 2010-09-24 19:28 ` Nicolas de Pesloüan 0 siblings, 0 replies; 24+ messages in thread From: Nicolas de Pesloüan @ 2010-09-24 19:28 UTC (permalink / raw) To: b43-dev Le 24/09/2010 20:39, Peter Stuge a ?crit : >> It is very complicated for French to understand all these subtleties! > > Maybe you can find a technical group in your area which can explain > it in your language. Even if it might sounds incredible, some other French guys read every mail in this mailing list and contribute from time to time. :-) So I translated to French and enhanced Peter's explanation for Cyrille, in a private mail. Nicolas. ^ permalink raw reply [flat|nested] 24+ messages in thread
end of thread, other threads:[~2010-09-24 19:28 UTC | newest]
Thread overview: 24+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-31 21:45 Problem with b43 Fabrizio Regalli
2010-06-01 2:17 ` William Bourque
2010-06-01 8:39 ` Martino Salvetti
2010-06-20 12:04 ` Fabrizio Regalli
2010-06-20 18:12 ` Gábor Stefanik
[not found] ` <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com>
2010-06-21 23:22 ` Gábor Stefanik
2010-06-22 15:09 ` Larry Finger
2010-06-22 18:54 ` Fabrizio Regalli
2010-06-22 19:46 ` Larry Finger
2010-06-22 20:40 ` Fabrizio Regalli
2010-06-24 21:50 ` Fabrizio Regalli
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 16:55 problem " Cyrille
2010-09-24 17:06 ` Gábor Stefanik
2010-09-24 17:21 ` John W. Linville
2010-09-24 17:30 ` Gábor Stefanik
2010-09-24 17:43 ` Michael Büsch
2010-09-24 17:39 ` Cyrille
2010-09-24 17:10 ` Rafał Miłecki
[not found] ` <20100924191547.59c58e7b.cyrille@cbiot.fr>
2010-09-24 17:28 ` Rafał Miłecki
2010-09-24 17:32 ` Cyrille
2010-09-24 17:46 ` Rafał Miłecki
2010-09-24 18:32 ` Cyrille
2010-09-24 18:39 ` Peter Stuge
2010-09-24 19:28 ` Nicolas de Pesloüan
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).