View previous topic :: View next topic |
Author |
Message |
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Sun Aug 17, 2014 4:58 am Post subject: Broadcom wireless driver |
|
|
Hi, ALL,
I have a DELL Inspiron laptop which has a Broadcom wireless network card.
Here is its info:
Code: |
lspci -vnn -d 14e4:
0c:00.0 Network controller [0280]: Broadcom Corporation BCM4312 802.11b/g LP-PHY [14e4:4315] (rev 01)
|
According to this this device is fully supported by the kernel.
Now according to this, I need to install b43-fwcutter and then, since I have gentoo-sources-3.12.20 on amd64 I need to install firmware from the Broadcom driver 5.100.138.
Now Gentoo has its own Broadcom WiKi page where it says I need to:
Code: |
echo "sys-firmware/b43-firmware" >> /etc/portage/package.accept_keywords
echo "sys-firmware/b43-firmware Broadcom" >> /etc/portage/package.license
emerge --ask b43-firmware
|
I did just that and it appears I have:
Code: |
emerge -pv b43-fwcutter b43-firmware
net-wireless/b43-fwcutter-018
sys-firmware/b43-firmware-6.30.163.46:b43
|
Now after installing those 2 and rebooting, I don't have a wireless enabled:
Code: |
lspci -v
0c:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g LP-PHY (rev 01)
Subsystem: Dell Wireless 1397 WLAN Mini-Card
Flags: bus master, fast devsel, latency 0, IRQ 17
Memory at f69fc000 (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 66-4a-5f-ff-ff-ce-00-22
Capabilities: [16c] Power Budgeting <?>
Kernel driver in use: b43-pci-bridge
dmesg | grep b43
b43-phy0: Broadcom 4312 WLAN found (core revision 15)
b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5 (LP), Revision 1)
b43: probe of ssb0:0 failed with error -95
|
The Broadcom driver compiled in the kernel.
And so it looks like this particular card is not supported by the kernel. Am I right?
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Sun Aug 17, 2014 6:24 am Post subject: |
|
|
Compile b43 as a module. _________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Tue Aug 19, 2014 9:39 am Post subject: |
|
|
Hi, logicien,
Code: |
IgorDellGentoo linux # cat .config | grep B43
CONFIG_B43=m
CONFIG_B43_SSB=y
CONFIG_B43_PCI_AUTOSELECT=y
CONFIG_B43_PCICORE_AUTOSELECT=y
# CONFIG_B43_PCMCIA is not set
CONFIG_B43_PIO=y
CONFIG_B43_PHY_N=y
CONFIG_B43_PHY_LP=y
CONFIG_B43_LEDS=y
CONFIG_B43_HWRNG=y
CONFIG_B43_DEBUG=y
# CONFIG_B43LEGACY is not set
CONFIG_SSB_B43_PCI_BRIDGE=y
|
Recompiled and rebooted.
Then issued:
modprobe b43
and nothing happened:
Code: |
IgorDellGentoo linux # ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::225:64ff:fe43:88f prefixlen 64 scopeid 0x20<link>
ether 00:25:64:43:08:8f txqueuelen 1000 (Ethernet)
RX packets 1951 bytes 1153440 (1.1 MiB)
RX errors 0 dropped 2 overruns 0 frame 0
TX packets 1594 bytes 205790 (200.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 2 bytes 100 (100.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 100 (100.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
|
What worries me is that lsmod does not give the b43 module after the modprobe.
So let me try to load it during boot.
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Tue Aug 19, 2014 2:27 pm Post subject: |
|
|
The question is that b43 must have access to the needed firmware files for your card at the moment it is loaded. If b43 is in the kernel image or in module in the initramfs, the firmware files should be in the kernel image too or at least in the initramfs.
If b43 is in module and not loaded before the real root partition is mounted, the firmware files should be in the root partition.
See the thread [Solved] wpa_supplicant not connecting. _________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Tue Aug 19, 2014 7:17 pm Post subject: |
|
|
Logicien,
Well, I did:
Code: |
echo "sys-firmware/b43-firmware" >> /etc/portage/package.accept_keywords
echo "sys-firmware/b43-firmware Broadcom" >> /etc/portage/package.license
emerge --ask b43-firmware
|
Are you saying that the firmware needs to be moved?
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Tue Aug 19, 2014 8:29 pm Post subject: |
|
|
I say that the firmware need to be whereis b43 and I think b43 should be in the real root partition as module with the firmware files in /lib/firmware/b43.
Otherwise, b43 can be load without access to firmware files. That will leave the wireless card in an unusable state. The b43 module can load later the firmware files when they will be available or you will have to stop any service who use your wireless card, unload b43 and load it again with the good firmware files available at the same time. _________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Wed Aug 20, 2014 2:56 am Post subject: |
|
|
Logicien,
I'm not sure I understand.
I have a firmware installed in /lib/firmware/b43. Are you saying that b43.ko should be in that same directory? If yes, than how do I load it on the boot-up process?
Please clarify.
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Wed Aug 20, 2014 3:30 am Post subject: |
|
|
No. I just say that b43 should be able to access the needed firmware files for your Broadcom wireless network card when it will probe the card.
It is the module, the b43 driver, who will flash the card, with the appropriate firmwares files, to be able to dialog with it. If the firmware files are not accessibles at the probe moment, b43 will fail to initialise the card.
If you compile b43 as a module and the good firmware files are in /lib/firmware/b43, everything should be ok. _________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Wed Aug 20, 2014 3:34 am Post subject: |
|
|
Logicien,
Now this is clear.
But I compiled the b43 as a module and a good firmware is in the lib/firmware/b43.
Code: |
IgorDellGentoo b43 # ls -la
total 1292
drwxr-xr-x 2 root root 12288 Aug 8 06:47 .
drwxr-xr-x 62 root root 12288 Aug 9 00:06 ..
-rw-r--r-- 1 root root 178 Aug 8 06:47 a0g0bsinitvals5.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 a0g0bsinitvals9.fw
-rw-r--r-- 1 root root 1836 Aug 8 06:47 a0g0initvals5.fw
-rw-r--r-- 1 root root 1992 Aug 8 06:47 a0g0initvals9.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 a0g1bsinitvals13.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 a0g1bsinitvals5.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 a0g1bsinitvals9.fw
-rw-r--r-- 1 root root 2170 Aug 8 06:47 a0g1initvals13.fw
-rw-r--r-- 1 root root 1836 Aug 8 06:47 a0g1initvals5.fw
-rw-r--r-- 1 root root 1992 Aug 8 06:47 a0g1initvals9.fw
-rw-r--r-- 1 root root 368 Aug 8 06:47 ac0bsinitvals40.fw
-rw-r--r-- 1 root root 3452 Aug 8 06:47 ac0initvals40.fw
-rw-r--r-- 1 root root 368 Aug 8 06:47 ac1bsinitvals42.fw
-rw-r--r-- 1 root root 3442 Aug 8 06:47 ac1initvals42.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 ac2bsinitvals41.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 ac2initvals41.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 ac3bsinitvals43.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 ac3initvals43.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 b0g0bsinitvals13.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 b0g0bsinitvals5.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 b0g0bsinitvals9.fw
-rw-r--r-- 1 root root 2170 Aug 8 06:47 b0g0initvals13.fw
-rw-r--r-- 1 root root 1836 Aug 8 06:47 b0g0initvals5.fw
-rw-r--r-- 1 root root 1992 Aug 8 06:47 b0g0initvals9.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 ht0bsinitvals26.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 ht0bsinitvals29.fw
-rw-r--r-- 1 root root 2770 Aug 8 06:47 ht0initvals26.fw
-rw-r--r-- 1 root root 2830 Aug 8 06:47 ht0initvals29.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn0bsinitvals24.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn0bsinitvals25.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn0bsinitvals26.fw
-rw-r--r-- 1 root root 3080 Aug 8 06:47 lcn0initvals24.fw
-rw-r--r-- 1 root root 3074 Aug 8 06:47 lcn0initvals25.fw
-rw-r--r-- 1 root root 2770 Aug 8 06:47 lcn0initvals26.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn1bsinitvals24.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn1bsinitvals25.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn1bsinitvals26.fw
-rw-r--r-- 1 root root 3080 Aug 8 06:47 lcn1initvals24.fw
-rw-r--r-- 1 root root 3074 Aug 8 06:47 lcn1initvals25.fw
-rw-r--r-- 1 root root 2770 Aug 8 06:47 lcn1initvals26.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn2bsinitvals24.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn2bsinitvals25.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lcn2bsinitvals26.fw
-rw-r--r-- 1 root root 3080 Aug 8 06:47 lcn2initvals24.fw
-rw-r--r-- 1 root root 3074 Aug 8 06:47 lcn2initvals25.fw
-rw-r--r-- 1 root root 2770 Aug 8 06:47 lcn2initvals26.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn400bsinitvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn400initvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn401bsinitvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn401initvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn402bsinitvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn402initvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn403bsinitvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn403initvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn404bsinitvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn404bsinitvals35.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn404initvals33.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn404initvals35.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn405bsinitvals35.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn405initvals35.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn406bsinitvals37.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn406initvals37.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn407bsinitvals38.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lcn407initvals38.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lp0bsinitvals13.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp0bsinitvals14.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lp0bsinitvals15.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 lp0bsinitvals16.fw
-rw-r--r-- 1 root root 3708 Aug 8 06:47 lp0initvals13.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp0initvals14.fw
-rw-r--r-- 1 root root 2642 Aug 8 06:47 lp0initvals15.fw
-rw-r--r-- 1 root root 2830 Aug 8 06:47 lp0initvals16.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp1bsinitvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp1bsinitvals22.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp1initvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp1initvals22.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp2bsinitvals19.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 lp2initvals19.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0absinitvals11.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0bsinitvals11.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0bsinitvals16.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0bsinitvals17.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n0bsinitvals22.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0bsinitvals24.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n0bsinitvals25.fw
-rw-r--r-- 1 root root 2196 Aug 8 06:47 n0initvals11.fw
-rw-r--r-- 1 root root 2830 Aug 8 06:47 n0initvals16.fw
-rw-r--r-- 1 root root 2500 Aug 8 06:47 n0initvals17.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n0initvals22.fw
-rw-r--r-- 1 root root 3080 Aug 8 06:47 n0initvals24.fw
-rw-r--r-- 1 root root 3074 Aug 8 06:47 n0initvals25.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 n16bsinitvals30.fw
-rw-r--r-- 1 root root 2672 Aug 8 06:47 n16initvals30.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n18bsinitvals32.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n18initvals32.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n19bsinitvals34.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n19initvals34.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n1bsinitvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n1initvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n20bsinitvals36.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n20initvals36.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n2bsinitvals19.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 n2initvals19.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 pcm4.fw
-rw-r--r-- 1 root root 1320 Aug 8 06:47 pcm5.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 sslpn0bsinitvals16.fw
-rw-r--r-- 1 root root 2830 Aug 8 06:47 sslpn0initvals16.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn1bsinitvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn1bsinitvals27.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn1initvals20.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn1initvals27.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn2bsinitvals19.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn2initvals19.fw
-rw-r--r-- 1 root root 178 Aug 8 06:47 sslpn3bsinitvals21.fw
-rw-r--r-- 1 root root 2644 Aug 8 06:47 sslpn3initvals21.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn4bsinitvals22.fw
-rw-r--r-- 1 root root 8 Aug 8 06:47 sslpn4initvals22.fw
-rw-r--r-- 1 root root 30752 Aug 8 06:47 ucode11.fw
-rw-r--r-- 1 root root 27880 Aug 8 06:47 ucode13.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode14.fw
-rw-r--r-- 1 root root 29080 Aug 8 06:47 ucode15.fw
-rw-r--r-- 1 root root 33776 Aug 8 06:47 ucode16_lp.fw
-rw-r--r-- 1 root root 39368 Aug 8 06:47 ucode16_mimo.fw
-rw-r--r-- 1 root root 34651 Aug 8 06:47 ucode16_sslpn.fw
-rw-r--r-- 1 root root 28708 Aug 8 06:47 ucode16_sslpn_nobt.fw
-rw-r--r-- 1 root root 36072 Aug 8 06:47 ucode17_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode19_sslpn.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode19_sslpn_nobt.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode20_sslpn.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode20_sslpn_nobt.fw
-rw-r--r-- 1 root root 29709 Aug 8 06:47 ucode21_sslpn.fw
-rw-r--r-- 1 root root 29709 Aug 8 06:47 ucode21_sslpn_nobt.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode22_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode22_sslpn.fw
-rw-r--r-- 1 root root 35106 Aug 8 06:47 ucode24_lcn.fw
-rw-r--r-- 1 root root 39976 Aug 8 06:47 ucode24_mimo.fw
-rw-r--r-- 1 root root 34399 Aug 8 06:47 ucode25_lcn.fw
-rw-r--r-- 1 root root 32048 Aug 8 06:47 ucode25_mimo.fw
-rw-r--r-- 1 root root 39704 Aug 8 06:47 ucode26_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode27_sslpn.fw
-rw-r--r-- 1 root root 43224 Aug 8 06:47 ucode29_mimo.fw
-rw-r--r-- 1 root root 40080 Aug 8 06:47 ucode30_mimo.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode32_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode33_lcn40.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode34_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode35_lcn40.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode36_mimo.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode37_lcn40.fw
-rw-r--r-- 1 root root 9 Aug 8 06:47 ucode38_lcn40.fw
-rw-r--r-- 1 root root 40584 Aug 8 06:47 ucode40.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode41.fw
-rw-r--r-- 1 root root 40024 Aug 8 06:47 ucode42.fw
-rw-r--r-- 1 root root 12 Aug 8 06:47 ucode43.fw
-rw-r--r-- 1 root root 21048 Aug 8 06:47 ucode5.fw
-rw-r--r-- 1 root root 24072 Aug 8 06:47 ucode9.fw
IgorDellGentoo b43 # pwd
/lib/firmware/b43
IgorDellGentoo b43 #
|
So what am I missing?
Maybe those files needs to be in /lib/firmware and not /lib/firmware/b43?
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Wed Aug 20, 2014 11:46 am Post subject: |
|
|
If you do
you can see which firmware files b43 is expecting. All of them are in the b43 directory relative to /lib/firmware. You can see too who are the modules from which b43 depend and check if they are available to be loaded and if they are activated in your kernel .config. With
you can check if b43 complain about missing firmware files. If I understand, you cannot use your Broadcom wireless card at this moment. Thus
show you something related to a wireless card? What about
_________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Thu Aug 21, 2014 2:09 am Post subject: |
|
|
Logicien,
Code: |
IgorDellGentoo b43 # modinfo b43
filename: /lib/modules/3.12.20-gentoo/kernel/drivers/net/wireless/b43/b43.ko
firmware: b43/ucode9.fw
firmware: b43/ucode5.fw
firmware: b43/ucode16_mimo.fw
firmware: b43/ucode15.fw
firmware: b43/ucode14.fw
firmware: b43/ucode13.fw
firmware: b43/ucode11.fw
license: GPL
author: RafaÅ MiÅecki
author: Gábor Stefanik
author: Michael Buesch
author: Stefano Brivio
author: Martin Langer
description: Broadcom B43 wireless driver
alias: ssb:v4243id0812rev10*
alias: ssb:v4243id0812rev0F*
alias: ssb:v4243id0812rev0D*
alias: ssb:v4243id0812rev0C*
alias: ssb:v4243id0812rev0B*
alias: ssb:v4243id0812rev0A*
alias: ssb:v4243id0812rev09*
alias: ssb:v4243id0812rev07*
alias: ssb:v4243id0812rev06*
alias: ssb:v4243id0812rev05*
depends:
intree: Y
vermagic: 3.12.20-gentoo SMP mod_unload
parm: bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm: fwpostfix:Postfix for the .fw files to load. (string)
parm: hwpctl:Enable hardware-side power control (default off) (int)
parm: nohwcrypt:Disable hardware encryption. (int)
parm: hwtkip:Enable hardware tkip. (int)
parm: qos:Enable QOS support (default on) (int)
parm: btcoex:Enable Bluetooth coexistence (default on) (int)
parm: verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)
parm: pio:Use PIO accesses by default: 0=DMA, 1=PIO (int)
parm: allhwsupport:Enable support for all hardware (even it if overlaps with the brcmsmac driver) (int)
|
As you can see there is no dependencies.
Yes, I can't use my wireless card. But:
Code: |
IgorDellGentoo b43 # ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::225:64ff:fe43:88f prefixlen 64 scopeid 0x20<link>
ether 00:25:64:43:08:8f txqueuelen 1000 (Ethernet)
RX packets 73506 bytes 20571286 (19.6 MiB)
RX errors 0 dropped 656 overruns 0 frame 0
TX packets 51605 bytes 6976214 (6.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 18
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 2 bytes 100 (100.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2 bytes 100 (100.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
sit0: flags=128<NOARP> mtu 1480
sit txqueuelen 0 (IPv6-in-IPv4)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
|
There is nothing about the wireless card.
Moreover, I have b43 debug turned on in kernel, but loading the module I don't see why it fails to be loaded.
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Thu Aug 21, 2014 7:37 am Post subject: |
|
|
What about something like
Code: | dmesg | grep -i -e b43 -e broad -e firm | less |
Do you see errors related to b43, Broadcom and firmware?
Everything in the kernel configuration related to wireless should be in module when possible, like CONFIG_CFG80211 and CONFIG_MAC80211. If b43 have no dependancy in your modinfo output, I suppose it's because you put all stuff that b43 depend on in hard in the kernel image.
In ArchLinux, the output of modinfo b43 show a lot of modules dependancies. They are all compiled as modules. That can make a difference. Dependancies from b43 should be compiled the same way than b43 itself, anything in module when possible.
Code: | modinfo b43
filename: /lib/modules/3.16.1-1-ARCH/kernel/drivers/net/wireless/b43/b43.ko.gz
firmware: b43/ucode9.fw
firmware: b43/ucode5.fw
firmware: b43/ucode16_mimo.fw
firmware: b43/ucode15.fw
firmware: b43/ucode14.fw
firmware: b43/ucode13.fw
firmware: b43/ucode11.fw
license: GPL
author: Rafał Miłecki
author: Gábor Stefanik
author: Michael Buesch
author: Stefano Brivio
author: Martin Langer
description: Broadcom B43 wireless driver
alias: ssb:v4243id0812rev10*
alias: ssb:v4243id0812rev0F*
alias: ssb:v4243id0812rev0D*
alias: ssb:v4243id0812rev0C*
alias: ssb:v4243id0812rev0B*
alias: ssb:v4243id0812rev0A*
alias: ssb:v4243id0812rev09*
alias: ssb:v4243id0812rev07*
alias: ssb:v4243id0812rev06*
alias: ssb:v4243id0812rev05*
alias: bcma:m04BFid0812rev1Dcl*
alias: bcma:m04BFid0812rev18cl*
alias: bcma:m04BFid0812rev17cl*
alias: bcma:m04BFid0812rev11cl*
alias: pcmcia:m02D0c0476f*fn*pfn*pa*pb*pc*pd*
alias: pcmcia:m02D0c0448f*fn*pfn*pa*pb*pc*pd*
depends: bcma,ssb,pcmcia,mac80211,led-class,mmc_core,cfg80211,rng-core
intree: Y
vermagic: 3.16.1-1-ARCH SMP preempt mod_unload modversions
parm: bad_frames_preempt:enable(1) / disable(0) Bad Frames Preemption (int)
parm: fwpostfix:Postfix for the .fw files to load. (string)
parm: hwpctl:Enable hardware-side power control (default off) (int)
parm: nohwcrypt:Disable hardware encryption. (int)
parm: hwtkip:Enable hardware tkip. (int)
parm: qos:Enable QOS support (default on) (int)
parm: btcoex:Enable Bluetooth coexistence (default on) (int)
parm: verbose:Log message verbosity: 0=error, 1=warn, 2=info(default), 3=debug (int)
parm: pio:Use PIO accesses by default: 0=DMA, 1=PIO (int)
parm: allhwsupport:Enable support for all hardware (even it if overlaps with the brcmsmac driver) (int) |
_________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Thu Aug 21, 2014 9:00 am Post subject: |
|
|
Logicien wrote: |
What about something like
Code: |
dmesg | grep -i -e b43 -e broad -e firm | less
|
Do you see errors related to b43, Broadcom and firmware?
|
Nope.
Here is the output:
Code: |
[ 0.061153] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.201461] acpi PNP0A03:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 1.330063] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work.
[ 1.346589] b43-phy0: Broadcom 4312 WLAN found (core revision 15)
[ 1.363251] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5 (LP), Revision 1)
[ 1.364925] b43: probe of ssb0:0 failed with error -95
[ 1.366477] Broadcom 43xx driver loaded [ Features: PL ]
|
Let me try to recompile the kernel and put everything in as the module....
Thank you. |
|
Back to top |
|
|
Logicien Veteran
Joined: 16 Sep 2005 Posts: 1555 Location: Montréal
|
Posted: Thu Aug 21, 2014 11:01 am Post subject: |
|
|
This line
Code: | [ 1.363251] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5 (LP), Revision 1) |
is saying the PHY version of your Broadcom chipset is unsupported.
If it do not work even when everything is in module, your card is unsupported. Check at http://wireless.kernel.org/ _________________ Paul |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Sun Aug 24, 2014 10:42 pm Post subject: |
|
|
Logicien,
This is what I got from b43 dev ML:
Quote: |
On Sat, 23 Aug 2014 20:56:17 -0700
Igor Korot <ikorot01@gmail.com> wrote:
> [ 1.419227] b43-phy0 ERROR: FOUND UNSUPPORTED PHY (Analog 6, Type 5
> (LP), Revision 1)
> [ 1.420925] b43: probe of ssb0:0 failed with error -95
>
> What is "error -95"?
-EOPNOTSUPP
See below.
> Maybe I have wrong firmware?
No. You are using the wrong kernel.
The relevant code section, that throws the error is:
> int unsupported = 0;
>...
> switch (phy_type) {
>...
> #ifdef CONFIG_B43_PHY_LP
> case B43_PHYTYPE_LP:
> if (phy_rev > 2)
> unsupported = 1;
> break;
> #endif
>...
> default:
> unsupported = 1;
> }
> if (unsupported) {
> b43err(dev->wl, "FOUND UNSUPPORTED PHY (Analog %u, Type %d (%s), Revision %u)\n",
> analog_type, phy_type, b43_phy_name(dev, phy_type),
> phy_rev);
> return -EOPNOTSUPP;
> }
So for this error to trigger, you would have to have revision 3 or later, which you don't,
or you would have to have a kernel without LP support compiled in.
Make sure you installed your kernel _and_ initramfs correctly.
Also make sure to boot the correct kernel
|
Now, here are the questions:
1. How do I check about initramfs?
2. How do I check if I installed the kernel correctly?
3. And what does it mean: "make sure to boot the correct kernel"?
Thank you. |
|
Back to top |
|
|
ONEEYEMAN Advocate
Joined: 01 Mar 2005 Posts: 3610
|
Posted: Thu Aug 28, 2014 3:44 am Post subject: |
|
|
Anybody?
Thank you. |
|
Back to top |
|
|
|