* b43 with Kernel 4.1?
@ 2015-09-14 15:48 Wifi User
2015-09-14 23:57 ` Larry Finger
0 siblings, 1 reply; 6+ messages in thread
From: Wifi User @ 2015-09-14 15:48 UTC (permalink / raw)
To: b43-dev
Hi,
did someone mange to get b43 running under kernel 4.1?
With an older kernel everything is perfect. After an upgrade to 4.1 my
wireless card doesn't seem to get recognized. :( - The firmware cutter used
broadcom-wl-6.30.163.46
I can clearly see the card with lspci but I don't get a wlan0 device.
---
09:00.0 Network controller [0280]: Broadcom Corporation BCM4322
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04a4]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at dfcfc000 (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
Kernel driver in use: b43-pci-bridge
---
Thx
Wifiuser
^ permalink raw reply [flat|nested] 6+ messages in thread
* b43 with Kernel 4.1?
2015-09-14 15:48 b43 with Kernel 4.1? Wifi User
@ 2015-09-14 23:57 ` Larry Finger
2015-09-24 18:00 ` Wifi User
0 siblings, 1 reply; 6+ messages in thread
From: Larry Finger @ 2015-09-14 23:57 UTC (permalink / raw)
To: b43-dev
On 09/14/2015 10:48 AM, Wifi User wrote:
> Hi,
>
> did someone mange to get b43 running under kernel 4.1?
>
> With an older kernel everything is perfect. After an upgrade to 4.1 my
> wireless card doesn't seem to get recognized. :( - The firmware cutter used
> broadcom-wl-6.30.163.46
>
> I can clearly see the card with lspci but I don't get a wlan0 device.
>
> ---
> 09:00.0 Network controller [0280]: Broadcom Corporation BCM4322
> 802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
> Subsystem: Broadcom Corporation Device [14e4:04a4]
> Flags: bus master, fast devsel, latency 0, IRQ 18
> Memory at dfcfc000 (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
> Kernel driver in use: b43-pci-bridge
Driver b43 works with kernel 4.1. Have you checked the output of dmesg to see if
there are any clues there?
If you built your own kernel, you may have missed a configuration parameter. On
my system, the command 'grep B43 .config' yields the following:
CONFIG_B43=m
CONFIG_B43_BCMA=y
CONFIG_B43_SSB=y
CONFIG_B43_BUSES_BCMA_AND_SSB=y
# CONFIG_B43_BUSES_BCMA is not set
# CONFIG_B43_BUSES_SSB is not set
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
CONFIG_B43_SDIO=y
CONFIG_B43_BCMA_PIO=y
CONFIG_B43_PIO=y
CONFIG_B43_PHY_G=y
CONFIG_B43_PHY_N=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_PHY_HT=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
# CONFIG_B43_DEBUG is not set
CONFIG_B43LEGACY=m
CONFIG_B43LEGACY_PCI_AUTOSELECT=y
CONFIG_B43LEGACY_PCICORE_AUTOSELECT=y
CONFIG_B43LEGACY_LEDS=y
CONFIG_B43LEGACY_HWRNG=y
# CONFIG_B43LEGACY_DEBUG is not set
CONFIG_B43LEGACY_DMA=y
CONFIG_B43LEGACY_PIO=y
CONFIG_B43LEGACY_DMA_AND_PIO_MODE=y
# CONFIG_B43LEGACY_DMA_MODE is not set
# CONFIG_B43LEGACY_PIO_MODE is not set
CONFIG_SSB_B43_PCI_BRIDGE=y
My guess is that CONFIG_B43_PHY_N was missed.
Larry
^ permalink raw reply [flat|nested] 6+ messages in thread
* b43 with Kernel 4.1?
2015-09-14 23:57 ` Larry Finger
@ 2015-09-24 18:00 ` Wifi User
2015-09-25 3:40 ` Rafał Miłecki
0 siblings, 1 reply; 6+ messages in thread
From: Wifi User @ 2015-09-24 18:00 UTC (permalink / raw)
To: b43-dev
Hi,
2015-09-15 1:57 GMT+02:00 Larry Finger <Larry.Finger@lwfinger.net>:
> Driver b43 works with kernel 4.1. Have you checked the output of dmesg to
> see if there are any clues there?
Thanks, I finally got it working by not compiling the b43 into the
kernel but compiled it as module.
But at the moment iwconfig doesn't recognize the card as a wifi one:
###
root at device:~# iwconfig wlan0
wlan0 no wireless extensions.
###
But with iw I'm able to scan for other wifi networks (iw dev wlan0
scan) and get them listed, too.
rfkill is installed and the
lspci -vnn
###
09:00.0 Network controller [0280]: Broadcom Corporation BCM4322
802.11a/b/g/n Wireless LAN Controller [14e4:432b] (rev 01)
Subsystem: Broadcom Corporation Device [14e4:04a4]
Flags: bus master, fast devsel, latency 0, IRQ 18
Memory at dfcfc000 (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
Kernel driver in use: b43-pci-bridge
###
lsmod
###
Module Size Used by
b43 332450 0
mac80211 283414 1 b43
video 10633 0
ata_generic 2270 0
pata_sch 1553 0
ide_pci_generic 1964 0
###
root at device:~# uname -a
Linux device 4.1.0 #3 SMP PREEMPT Thu Sep 24 15:49:42 CEST 2015 i686 GNU/Linux
root at device:~# dmesg | grep b43
[ 11.321316] bus: 'bcma': add driver b43
[ 11.321451] bus: 'ssb': add driver b43
[ 11.321480] bus: 'ssb': driver_probe_device: matched device ssb0:0
with driver b43
[ 11.321491] bus: 'ssb': really_probe: probing driver b43 with device ssb0:0
[ 11.321513] b43 ssb0:0: no default pinctrl state
[ 11.321622] b43-phy0: Broadcom 4322 WLAN found (core revision 16)
[ 11.337966] b43-phy0: Found PHY: Analog 8, Type 4 (N), Revision 4
[ 11.338287] b43-phy0: Found Radio: Manuf 0x17F, ID 0x2056, Revision
3, Version 0
[ 11.346149] driver: 'b43': driver_bound: bound to device 'ssb0:0'
[ 11.346235] __allocate_fw_buf: fw-b43/ucode16_mimo.fw buf=de2f7f00
[ 11.346494] bus: 'ssb': really_probe: bound device ssb0:0 to driver b43
[ 11.364982] b43 ssb0:0: firmware: direct-loading firmware b43/ucode16_mimo.fw
[ 11.365002] fw_set_page_data: fw-b43/ucode16_mimo.fw buf=de2f7f00
data=e0324000 size=39296
[ 11.365129] __allocate_fw_buf: fw-b43/n0initvals16.fw buf=dd058b80
[ 11.367428] b43 ssb0:0: firmware: direct-loading firmware b43/n0initvals16.fw
[ 11.367448] fw_set_page_data: fw-b43/n0initvals16.fw buf=dd058b80
data=e00fd000 size=2738
[ 11.367469] __allocate_fw_buf: fw-b43/n0bsinitvals16.fw buf=dd743640
[ 11.369810] b43 ssb0:0: firmware: direct-loading firmware
b43/n0bsinitvals16.fw
[ 11.369830] fw_set_page_data: fw-b43/n0bsinitvals16.fw buf=dd743640
data=e032f000 size=178
[ 11.372400] device: 'b43-phy0::tx': device_add
[ 11.372605] device: 'b43-phy0::rx': device_add
[ 11.372822] device: 'b43-phy0::radio': device_add
root at device:~# ip link set link dev wlan0 up
[ 69.884173] b43-phy0: Loading firmware version 666.2 (2011-02-23 01:15:07)
root at device:~# iwconfig wlan0
wlan0 no wireless extensions.
Do you happen to have a clue where I'm doing something wrong?
Thanks and kind Regards
^ permalink raw reply [flat|nested] 6+ messages in thread
* b43 with Kernel 4.1?
2015-09-24 18:00 ` Wifi User
@ 2015-09-25 3:40 ` Rafał Miłecki
2015-09-25 6:39 ` Wifi User
0 siblings, 1 reply; 6+ messages in thread
From: Rafał Miłecki @ 2015-09-25 3:40 UTC (permalink / raw)
To: b43-dev
On 24 September 2015 at 20:00, Wifi User <mywifiismycastle@gmail.com> wrote:
> Do you happen to have a clue where I'm doing something wrong?
You're trying to use obsolete API (iwconfig). Just stick to nl80211
(it's used by "iw" tool and wpa_supplicant with "-D nl80211").
--
Rafa?
^ permalink raw reply [flat|nested] 6+ messages in thread
* b43 with Kernel 4.1?
2015-09-25 3:40 ` Rafał Miłecki
@ 2015-09-25 6:39 ` Wifi User
2015-09-25 7:11 ` Rafał Miłecki
0 siblings, 1 reply; 6+ messages in thread
From: Wifi User @ 2015-09-25 6:39 UTC (permalink / raw)
To: b43-dev
Thanks Rafa?!
Switching to nl80211 finally solved it!
2015-09-25 5:40 GMT+02:00 Rafa? Mi?ecki <zajec5@gmail.com>:
> On 24 September 2015 at 20:00, Wifi User <mywifiismycastle@gmail.com> wrote:
>> Do you happen to have a clue where I'm doing something wrong?
>
> You're trying to use obsolete API (iwconfig). Just stick to nl80211
> (it's used by "iw" tool and wpa_supplicant with "-D nl80211").
That means in future I shouldn't use iwconfig any longer but switch to
iw wlan0 link instead?
Next challenge is getting 802.11n to run. - Are there any plans to
support 802.11n with b43, too?
(My chip 14e4:432b is unfortunately not supported by brcm80211 :()
^ permalink raw reply [flat|nested] 6+ messages in thread
* b43 with Kernel 4.1?
2015-09-25 6:39 ` Wifi User
@ 2015-09-25 7:11 ` Rafał Miłecki
0 siblings, 0 replies; 6+ messages in thread
From: Rafał Miłecki @ 2015-09-25 7:11 UTC (permalink / raw)
To: b43-dev
On 25 September 2015 at 08:39, Wifi User <mywifiismycastle@gmail.com> wrote:
> 2015-09-25 5:40 GMT+02:00 Rafa? Mi?ecki <zajec5@gmail.com>:
>> On 24 September 2015 at 20:00, Wifi User <mywifiismycastle@gmail.com> wrote:
>>> Do you happen to have a clue where I'm doing something wrong?
>>
>> You're trying to use obsolete API (iwconfig). Just stick to nl80211
>> (it's used by "iw" tool and wpa_supplicant with "-D nl80211").
>
> That means in future I shouldn't use iwconfig any longer but switch to
> iw wlan0 link instead?
https://wireless.wiki.kernel.org/en/developers/documentation/nl80211
> Next challenge is getting 802.11n to run. - Are there any plans to
> support 802.11n with b43, too?
> (My chip 14e4:432b is unfortunately not supported by brcm80211 :()
A little chance for that, I'm too busy with other stuff.
--
Rafa?
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-09-25 7:11 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-09-14 15:48 b43 with Kernel 4.1? Wifi User
2015-09-14 23:57 ` Larry Finger
2015-09-24 18:00 ` Wifi User
2015-09-25 3:40 ` Rafał Miłecki
2015-09-25 6:39 ` Wifi User
2015-09-25 7:11 ` Rafał Miłecki
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).