* BCM4318KFBG not recognized by b43
@ 2010-10-20 19:28 Daniel Klaffenbach
2010-10-20 21:21 ` Gábor Stefanik
0 siblings, 1 reply; 10+ messages in thread
From: Daniel Klaffenbach @ 2010-10-20 19:28 UTC (permalink / raw)
To: b43-dev
Hi,
I just got a new Mini-PCI wireless card which does not seem to be
supported by b43 yet. On the chipset it says "BCM4318KFBG". I suspect
the vendor id of the card is causing trouble - it is 14a4 (GVC/BCM
Advanced Research) instead of the usual 14e4.
root at OpenWrt:~# uname -a
Linux OpenWrt 2.6.34.7 #1 Wed Oct 20 16:10:32 CEST 2010 mips GNU/Linux
root at OpenWrt:~# lspci -vvn
00:02.0 0280: 14a4:4318 (rev 02)
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-
Interrupt: pin A routed to IRQ 0
Region 0: Memory at 40000000 (32-bit, non-prefetchable)
[disabled] [size=8K]
I've already tried to force the b43-pci-bridge to use this device, but
it resulted in a kernel Oops (I don't know if that made sense anyway):
root@OpenWrt:~# echo '14a4 4318' > /sys/bus/pci/drivers/b43-pci-bridge/new_id
PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
PCI: Fixing up device 0000:00:02.0
PCI: Setting latency timer of device 0000:00:02.0 to 64
ssb: PCI-ID not in fallback list
ssb: CHIPID not in nrcores fallback list
ssb: Core 0 found: UNKNOWN (cc 0x014, rev 0x00, vendor 0x0000)
Data bus error, epc == 8013e404, ra == 80188ff8
Oops[#1]:
Cpu 0
$ 0 : 00000000 1000bc00 00000000 00000018
$ 4 : c0a05018 804ef300 00000000 00000000
$ 8 : 00000000 80005510 00000002 8026e000
$12 : 80273920 00000002 00000001 00000002
$16 : 0000000d 804ef318 80d26c00 80d26f84
$20 : 80d26c00 80239ce4 80637f10 805dde18
$24 : 3b9aca00 80014630
$28 : 80636000 80637c68 00467034 80188ff8
Hi : 00000068
Lo : 4a59d500
epc : 8013e404 0x8013e404
Not tainted
ra : 80188ff8 0x80188ff8
Status: 1000bc03 KERNEL EXL IE
Cause : 0080001c
PrId : 00024000 (Broadcom BCM4710)
Modules linked in: usb_storage ohci_hcd ip6t_REJECT ip6t_LOG ip6t_rt
ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah
ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables
nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc
nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_iprange xt_string
ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack sd_mod ipt_REJECT
xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit
iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ext2
tunnel4 ext3 jbd tun vfat fat ext4 jbd2 b43 nls_utf8 mac80211 usbcore
ts_fsm ts_bm ts_kmp switch_core scsi_mod nls_base mbcache crc16
cfg80211 compat arc4 aes_generic deflate ecb cbc ipv6 diag [last
unloaded: switch_core]
Process ash (pid: 1708, threadinfo=80636000, task=8030aa58, tls=00000000)
Stack : 80637c98 80354d48 00000000 80637cc8 fffffff4 804ef300 80637cc8 80189568
00000000 00000000 80637cc8 00000000 80d26c00 80637cc8 00000000 80d26c00
80d26f84 801894b0 80239ce4 8018753c 00000037 80023e74 1000bc00 00000001
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
...
Call Trace:[<80189568>] 0x80189568
[<801894b0>] 0x801894b0
[<8018753c>] 0x8018753c
[<80023e74>] 0x80023e74
[<8018771c>] 0x8018771c
[<8018a370>] 0x8018a370
[<8014533c>] 0x8014533c
[<801453b4>] 0x801453b4
[<801673d4>] 0x801673d4
[<80167598>] 0x80167598
[<8016774c>] 0x8016774c
[<801676e0>] 0x801676e0
[<80166c90>] 0x80166c90
[<800798b8>] 0x800798b8
[<80145770>] 0x80145770
[<80127e24>] 0x80127e24
[<8014589c>] 0x8014589c
[<80016bb4>] 0x80016bb4
[<800dea68>] 0x800dea68
[<80090fac>] 0x80090fac
[<8009ed20>] 0x8009ed20
[<80003630>] 0x80003630
[<8002727c>] 0x8002727c
Code: 90820000 03e00008 304200ff <94820000> 03e00008 3042ffff
94820000 3042ffff 00021a02
Disabling lock debugging due to kernel taint
The full dmesg output of the device is available at http://pastebin.ca/1968330.
Is there anything else I can do to get the device to work? I'd be
happy to test any patches but please keep in mind that my distribution
(OpenWRT) requires me to use Linux 2.6.34 at the moment (which is the
most current version for BCM47xx in OpenWRT trunk).
Regards,
Daniel
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-10-20 19:28 BCM4318KFBG not recognized by b43 Daniel Klaffenbach
@ 2010-10-20 21:21 ` Gábor Stefanik
2010-10-20 22:43 ` Daniel Klaffenbach
0 siblings, 1 reply; 10+ messages in thread
From: Gábor Stefanik @ 2010-10-20 21:21 UTC (permalink / raw)
To: b43-dev
On Wed, Oct 20, 2010 at 9:28 PM, Daniel Klaffenbach
<danielklaffenbach@gmail.com> wrote:
> Hi,
>
> I just got a new Mini-PCI wireless card which does not seem to be
> supported by b43 yet. On the chipset it says "BCM4318KFBG". I suspect
> the vendor id of the card is causing trouble - it is 14a4 (GVC/BCM
> Advanced Research) instead of the usual 14e4.
>
> root at OpenWrt:~# uname -a
> Linux OpenWrt 2.6.34.7 #1 Wed Oct 20 16:10:32 CEST 2010 mips GNU/Linux
>
> root at OpenWrt:~# lspci -vvn
> 00:02.0 0280: 14a4:4318 (rev 02)
> ? ? ? ?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-
> ? ? ? ?Interrupt: pin A routed to IRQ 0
> ? ? ? ?Region 0: Memory at 40000000 (32-bit, non-prefetchable)
> [disabled] [size=8K]
>
>
> I've already tried to force the b43-pci-bridge to use this device, but
> it resulted in a kernel Oops (I don't know if that made sense anyway):
>
> root at OpenWrt:~# echo '14a4 4318' > /sys/bus/pci/drivers/b43-pci-bridge/new_id
> PCI: Enabling device 0000:00:02.0 (0000 -> 0002)
> PCI: Fixing up device 0000:00:02.0
> PCI: Setting latency timer of device 0000:00:02.0 to 64
> ssb: PCI-ID not in fallback list
> ssb: CHIPID not in nrcores fallback list
> ssb: Core 0 found: UNKNOWN (cc 0x014, rev 0x00, vendor 0x0000)
> Data bus error, epc == 8013e404, ra == 80188ff8
> Oops[#1]:
> Cpu 0
> $ 0 ? : 00000000 1000bc00 00000000 00000018
> $ 4 ? : c0a05018 804ef300 00000000 00000000
> $ 8 ? : 00000000 80005510 00000002 8026e000
> $12 ? : 80273920 00000002 00000001 00000002
> $16 ? : 0000000d 804ef318 80d26c00 80d26f84
> $20 ? : 80d26c00 80239ce4 80637f10 805dde18
> $24 ? : 3b9aca00 80014630
> $28 ? : 80636000 80637c68 00467034 80188ff8
> Hi ? ?: 00000068
> Lo ? ?: 4a59d500
> epc ? : 8013e404 0x8013e404
> ? ?Not tainted
> ra ? ?: 80188ff8 0x80188ff8
> Status: 1000bc03 ? ?KERNEL EXL IE
> Cause : 0080001c
> PrId ?: 00024000 (Broadcom BCM4710)
> Modules linked in: usb_storage ohci_hcd ip6t_REJECT ip6t_LOG ip6t_rt
> ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah
> ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables
> nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc
> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_iprange xt_string
> ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
> nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack sd_mod ipt_REJECT
> xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit
> iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ext2
> tunnel4 ext3 jbd tun vfat fat ext4 jbd2 b43 nls_utf8 mac80211 usbcore
> ts_fsm ts_bm ts_kmp switch_core scsi_mod nls_base mbcache crc16
> cfg80211 compat arc4 aes_generic deflate ecb cbc ipv6 diag [last
> unloaded: switch_core]
> Process ash (pid: 1708, threadinfo=80636000, task=8030aa58, tls=00000000)
> Stack : 80637c98 80354d48 00000000 80637cc8 fffffff4 804ef300 80637cc8 80189568
> ? ? ? ?00000000 00000000 80637cc8 00000000 80d26c00 80637cc8 00000000 80d26c00
> ? ? ? ?80d26f84 801894b0 80239ce4 8018753c 00000037 80023e74 1000bc00 00000001
> ? ? ? ?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> ? ? ? ?00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> ? ? ? ?...
> Call Trace:[<80189568>] 0x80189568
> [<801894b0>] 0x801894b0
> [<8018753c>] 0x8018753c
> [<80023e74>] 0x80023e74
> [<8018771c>] 0x8018771c
> [<8018a370>] 0x8018a370
> [<8014533c>] 0x8014533c
> [<801453b4>] 0x801453b4
> [<801673d4>] 0x801673d4
> [<80167598>] 0x80167598
> [<8016774c>] 0x8016774c
> [<801676e0>] 0x801676e0
> [<80166c90>] 0x80166c90
> [<800798b8>] 0x800798b8
> [<80145770>] 0x80145770
> [<80127e24>] 0x80127e24
> [<8014589c>] 0x8014589c
> [<80016bb4>] 0x80016bb4
> [<800dea68>] 0x800dea68
> [<80090fac>] 0x80090fac
> [<8009ed20>] 0x8009ed20
> [<80003630>] 0x80003630
> [<8002727c>] 0x8002727c
>
> Code: 90820000 ?03e00008 ?304200ff <94820000> 03e00008 ?3042ffff
> 94820000 ?3042ffff ?00021a02
> Disabling lock debugging due to kernel taint
Hmm, that sounds like a defective card... I've previously seen an Asus
WL-138G V2 identify itself, first as 14e4:4218, then after a repair
attempt, 14e4:0008. It also produced errors like this when I forced
its detection.
>
>
> The full dmesg output of the device is available at http://pastebin.ca/1968330.
>
> Is there anything else I can do to get the device to work? I'd be
> happy to test any patches but please keep in mind that my distribution
> (OpenWRT) requires me to use Linux 2.6.34 at the moment (which is the
> most current version for BCM47xx in OpenWRT trunk).
>
>
> Regards,
> Daniel
>
> _______________________________________________
> 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] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-10-20 21:21 ` Gábor Stefanik
@ 2010-10-20 22:43 ` Daniel Klaffenbach
2010-10-22 9:15 ` Daniel Klaffenbach
0 siblings, 1 reply; 10+ messages in thread
From: Daniel Klaffenbach @ 2010-10-20 22:43 UTC (permalink / raw)
To: b43-dev
> Hmm, that sounds like a defective card... I've previously seen an Asus
> WL-138G V2 identify itself, first as 14e4:4218, then after a repair
> attempt, 14e4:0008. It also produced errors like this when I forced
> its detection.
I've just tried the card with the proprietary Broadcom driver and it
is working quite well with it - so I can definitely say that the card
is working. With the "wl" driver the card is being recognized as "wl0:
Broadcom BCM4318 802.11 Wireless Controller 5.10.56.27".
Regards,
Daniel
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-10-20 22:43 ` Daniel Klaffenbach
@ 2010-10-22 9:15 ` Daniel Klaffenbach
2010-10-22 20:16 ` Larry Finger
0 siblings, 1 reply; 10+ messages in thread
From: Daniel Klaffenbach @ 2010-10-22 9:15 UTC (permalink / raw)
To: b43-dev
I got a little bit further by adding the vendor id to
b43_pci_bridge.c. Note that it now detects the card correctly (4318).
root at OpenWrt:/# modprobe b43
Segmentation fault
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
Data bus error, epc == 8013e42c, ra == 80784704
Oops[#1]:
Cpu 0
$ 0 : 00000000 1000bc00 200002ff 00000000
$ 4 : c0000f9c 00000004 0c040083 00000000
$ 8 : 00000010 00000080 00000004 8026e000
$12 : 80273920 00000002 00000001 00000002
$16 : 80e7ad00 802e7000 00000000 807a013c
$20 : 8027a6f4 00000000 00407ed4 00000000
$24 : 3b9aca00 80014630
$28 : 802a0000 802a1d48 80e7ad00 80784704
Hi : 00000018
Lo : 52101200
epc : 8013e42c 0x8013e42c
Not tainted
ra : 80784704 0x80784704
Status: 1000bc03 KERNEL EXL IE
Cause : 0080001c
PrId : 00024000 (Broadcom BCM4710)
Modules linked in: b43(+) usb_storage ohci_hcd ip6t_REJECT ip6t_LOG
ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah
ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables
nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc
nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_iprange xt_string
ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack sd_mod ipt_REJECT
xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit
iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ext2
tunnel4 ext3 jbd nls_utf8 mac80211 usbcore ts_fsm ts_bm ts_kmp
switch_core scsi_mod nls_base mbcache crc16 cfg80211 compat arc4
aes_generic deflate ecb cbc ipv6 diag [last unloaded: switch_core]
Process insmod (pid: 1115, threadinfo=802a0000, task=80dc5a38, tls=00000000)
Stack : 00000662 800dfefc 00004318 00000009 80a27f84 80a27f2c 00000000 80e7ad00
80851000 80851400 80e7ad88 802e72f8 00000001 806f4380 807a0120 80851058
807a013c 807a013c 8027a6f4 00000000 00407ed4 00000002 7fb5beb8 80186954
80851058 806f4380 fffffffe 802542cc ffffffed ffffffed 80855180 80167598
8027a6f4 80122cf8 80340010 00000004 808551b4 80855180 807a013c 8016774c
...
Call Trace:[<800dfefc>] 0x800dfefc
[<80186954>] 0x80186954
[<80167598>] 0x80167598
[<80122cf8>] 0x80122cf8
[<8016774c>] 0x8016774c
[<80122d40>] 0x80122d40
[<801676e0>] 0x801676e0
[<80166c90>] 0x80166c90
[<80122dd0>] 0x80122dd0
[<80166458>] 0x80166458
[<80083d38>] 0x80083d38
[<80632000>] 0x80632000
[<80167adc>] 0x80167adc
[<80055054>] 0x80055054
[<80632000>] 0x80632000
[<80632020>] 0x80632020
[<8000c4e0>] 0x8000c4e0
[<8004271c>] 0x8004271c
[<80055730>] 0x80055730
[<8008e040>] 0x8008e040
[<80003630>] 0x80003630
Code: 00431025 03e00008 3042ffff <8c820000> 03e00008 00000000
8c820000 00022e00 00022602
Disabling lock debugging due to kernel taint
I have attached the patch to add the vendor pci id. I am probably
still missing something, though.
Regards,
Daniel
diff --git a/drivers/ssb/b43_pci_bridge.c b/drivers/ssb/b43_pci_bridge.c
index ef9c6a0..744d3f6 100644
--- a/drivers/ssb/b43_pci_bridge.c
+++ b/drivers/ssb/b43_pci_bridge.c
@@ -24,6 +24,7 @@ static const struct pci_device_id b43_pci_bridge_tbl[] = {
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4312) },
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4315) },
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4318) },
+ { PCI_DEVICE(PCI_VENDOR_ID_BCM_GVC, 0x4318) },
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4319) },
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4320) },
{ PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, 0x4321) },
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 570fdde..d3c1cea 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -2041,6 +2041,7 @@
#define PCI_DEVICE_ID_AFAVLAB_P030 0x2182
#define PCI_SUBDEVICE_ID_AFAVLAB_P061 0x2150
+#define PCI_VENDOR_ID_BCM_GVC 0x14a4
#define PCI_VENDOR_ID_BROADCOM 0x14e4
#define PCI_DEVICE_ID_TIGON3_5752 0x1600
#define PCI_DEVICE_ID_TIGON3_5752M 0x1601
^ permalink raw reply related [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-10-22 9:15 ` Daniel Klaffenbach
@ 2010-10-22 20:16 ` Larry Finger
2010-11-17 21:39 ` Rafał Miłecki
0 siblings, 1 reply; 10+ messages in thread
From: Larry Finger @ 2010-10-22 20:16 UTC (permalink / raw)
To: b43-dev
On 10/22/2010 04:15 AM, Daniel Klaffenbach wrote:
> I got a little bit further by adding the vendor id to
> b43_pci_bridge.c. Note that it now detects the card correctly (4318).
>
> root at OpenWrt:/# modprobe b43
> Segmentation fault
>
> b43-phy0: Broadcom 4318 WLAN found (core revision 9)
> Data bus error, epc == 8013e42c, ra == 80784704
> Oops[#1]:
> Cpu 0
> $ 0 : 00000000 1000bc00 200002ff 00000000
> $ 4 : c0000f9c 00000004 0c040083 00000000
> $ 8 : 00000010 00000080 00000004 8026e000
> $12 : 80273920 00000002 00000001 00000002
> $16 : 80e7ad00 802e7000 00000000 807a013c
> $20 : 8027a6f4 00000000 00407ed4 00000000
> $24 : 3b9aca00 80014630
> $28 : 802a0000 802a1d48 80e7ad00 80784704
> Hi : 00000018
> Lo : 52101200
> epc : 8013e42c 0x8013e42c
> Not tainted
> ra : 80784704 0x80784704
> Status: 1000bc03 KERNEL EXL IE
> Cause : 0080001c
> PrId : 00024000 (Broadcom BCM4710)
> Modules linked in: b43(+) usb_storage ohci_hcd ip6t_REJECT ip6t_LOG
> ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah
> ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables
> nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc
> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_iprange xt_string
> ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
> nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack sd_mod ipt_REJECT
> xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit
> iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ext2
> tunnel4 ext3 jbd nls_utf8 mac80211 usbcore ts_fsm ts_bm ts_kmp
> switch_core scsi_mod nls_base mbcache crc16 cfg80211 compat arc4
> aes_generic deflate ecb cbc ipv6 diag [last unloaded: switch_core]
> Process insmod (pid: 1115, threadinfo=802a0000, task=80dc5a38, tls=00000000)
> Stack : 00000662 800dfefc 00004318 00000009 80a27f84 80a27f2c 00000000 80e7ad00
> 80851000 80851400 80e7ad88 802e72f8 00000001 806f4380 807a0120 80851058
> 807a013c 807a013c 8027a6f4 00000000 00407ed4 00000002 7fb5beb8 80186954
> 80851058 806f4380 fffffffe 802542cc ffffffed ffffffed 80855180 80167598
> 8027a6f4 80122cf8 80340010 00000004 808551b4 80855180 807a013c 8016774c
> ...
> Call Trace:[<800dfefc>] 0x800dfefc
> [<80186954>] 0x80186954
> [<80167598>] 0x80167598
> [<80122cf8>] 0x80122cf8
> [<8016774c>] 0x8016774c
> [<80122d40>] 0x80122d40
> [<801676e0>] 0x801676e0
> [<80166c90>] 0x80166c90
> [<80122dd0>] 0x80122dd0
> [<80166458>] 0x80166458
> [<80083d38>] 0x80083d38
> [<80632000>] 0x80632000
> [<80167adc>] 0x80167adc
> [<80055054>] 0x80055054
> [<80632000>] 0x80632000
> [<80632020>] 0x80632020
> [<8000c4e0>] 0x8000c4e0
> [<8004271c>] 0x8004271c
> [<80055730>] 0x80055730
> [<8008e040>] 0x8008e040
> [<80003630>] 0x80003630
Any chance of getting these addresses translated into something a bit more
symbolic? There is a package that does this, but I don't remember the name. Can
anyone help with that part?
Larry
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-10-22 20:16 ` Larry Finger
@ 2010-11-17 21:39 ` Rafał Miłecki
2010-11-17 22:48 ` Daniel Klaffenbach
0 siblings, 1 reply; 10+ messages in thread
From: Rafał Miłecki @ 2010-11-17 21:39 UTC (permalink / raw)
To: b43-dev
2010/10/22 Larry Finger <Larry.Finger@lwfinger.net>:
> On 10/22/2010 04:15 AM, Daniel Klaffenbach wrote:
>> I got a little bit further by adding the vendor id to
>> b43_pci_bridge.c. Note that it now detects the card correctly (4318).
>>
>> root at OpenWrt:/# modprobe b43
>> Segmentation fault
>>
>> b43-phy0: Broadcom 4318 WLAN found (core revision 9)
>> Data bus error, epc == 8013e42c, ra == 80784704
>> Oops[#1]:
>> Cpu 0
>> $ 0 ? : 00000000 1000bc00 200002ff 00000000
>> $ 4 ? : c0000f9c 00000004 0c040083 00000000
>> $ 8 ? : 00000010 00000080 00000004 8026e000
>> $12 ? : 80273920 00000002 00000001 00000002
>> $16 ? : 80e7ad00 802e7000 00000000 807a013c
>> $20 ? : 8027a6f4 00000000 00407ed4 00000000
>> $24 ? : 3b9aca00 80014630
>> $28 ? : 802a0000 802a1d48 80e7ad00 80784704
>> Hi ? ?: 00000018
>> Lo ? ?: 52101200
>> epc ? : 8013e42c 0x8013e42c
>> ? ? Not tainted
>> ra ? ?: 80784704 0x80784704
>> Status: 1000bc03 ? ?KERNEL EXL IE
>> Cause : 0080001c
>> PrId ?: 00024000 (Broadcom BCM4710)
>> Modules linked in: b43(+) usb_storage ohci_hcd ip6t_REJECT ip6t_LOG
>> ip6t_rt ip6t_hbh ip6t_mh ip6t_ipv6header ip6t_frag ip6t_eui64 ip6t_ah
>> ip6table_raw ip6_queue ip6table_mangle ip6table_filter ip6_tables
>> nf_conntrack_ipv6 nf_nat_tftp nf_conntrack_tftp nf_nat_irc
>> nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp xt_iprange xt_string
>> ipt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state
>> nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack sd_mod ipt_REJECT
>> xt_TCPMSS ipt_LOG xt_comment xt_multiport xt_mac xt_limit
>> iptable_mangle iptable_filter ip_tables xt_tcpudp x_tables sit ext2
>> tunnel4 ext3 jbd nls_utf8 mac80211 usbcore ts_fsm ts_bm ts_kmp
>> switch_core scsi_mod nls_base mbcache crc16 cfg80211 compat arc4
>> aes_generic deflate ecb cbc ipv6 diag [last unloaded: switch_core]
>> Process insmod (pid: 1115, threadinfo=802a0000, task=80dc5a38, tls=00000000)
>> Stack : 00000662 800dfefc 00004318 00000009 80a27f84 80a27f2c 00000000 80e7ad00
>> ? ? ? ? 80851000 80851400 80e7ad88 802e72f8 00000001 806f4380 807a0120 80851058
>> ? ? ? ? 807a013c 807a013c 8027a6f4 00000000 00407ed4 00000002 7fb5beb8 80186954
>> ? ? ? ? 80851058 806f4380 fffffffe 802542cc ffffffed ffffffed 80855180 80167598
>> ? ? ? ? 8027a6f4 80122cf8 80340010 00000004 808551b4 80855180 807a013c 8016774c
>> ? ? ? ? ...
>> Call Trace:[<800dfefc>] 0x800dfefc
>> [<80186954>] 0x80186954
>> [<80167598>] 0x80167598
>> [<80122cf8>] 0x80122cf8
>> [<8016774c>] 0x8016774c
>> [<80122d40>] 0x80122d40
>> [<801676e0>] 0x801676e0
>> [<80166c90>] 0x80166c90
>> [<80122dd0>] 0x80122dd0
>> [<80166458>] 0x80166458
>> [<80083d38>] 0x80083d38
>> [<80632000>] 0x80632000
>> [<80167adc>] 0x80167adc
>> [<80055054>] 0x80055054
>> [<80632000>] 0x80632000
>> [<80632020>] 0x80632020
>> [<8000c4e0>] 0x8000c4e0
>> [<8004271c>] 0x8004271c
>> [<80055730>] 0x80055730
>> [<8008e040>] 0x8008e040
>> [<80003630>] 0x80003630
>
> Any chance of getting these addresses translated into something a bit more
> symbolic? There is a package that does this, but I don't remember the name. Can
> anyone help with that part?
Daniel: anything new on this? Could you put that card in some "normal"
machine where it's relatively easy to install deubgging symbols?
--
Rafa?
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-11-17 21:39 ` Rafał Miłecki
@ 2010-11-17 22:48 ` Daniel Klaffenbach
2010-11-17 23:10 ` Rafał Miłecki
0 siblings, 1 reply; 10+ messages in thread
From: Daniel Klaffenbach @ 2010-11-17 22:48 UTC (permalink / raw)
To: b43-dev
On Wednesday 17 November 2010 22:39:31 Rafa? Mi?ecki wrote:
> Daniel: anything new on this? Could you put that card in some "normal"
> machine where it's relatively easy to install deubgging symbols?
I'm afraid no. My wireless router is the only machine in my environment with a
mini-PCI slot.
I could however compile the kernel for my OpenWRT box with debugging symbols
(KERNEL_DEBUG_INFO in OpenWRT config), if this helps.
Could the PCI vendor id alone be the reason for this problem? As I mentioned
earlier I've added the ID to b43_pci_bridge.c, but I am not sure whether this
is sufficient or not.
Regards,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20101117/707eee94/attachment.sig>
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-11-17 22:48 ` Daniel Klaffenbach
@ 2010-11-17 23:10 ` Rafał Miłecki
2010-11-17 23:23 ` Larry Finger
2010-11-19 17:26 ` Daniel Klaffenbach
0 siblings, 2 replies; 10+ messages in thread
From: Rafał Miłecki @ 2010-11-17 23:10 UTC (permalink / raw)
To: b43-dev
W dniu 17 listopada 2010 23:48 u?ytkownik Daniel Klaffenbach
<danielklaffenbach@gmail.com> napisa?:
> On Wednesday 17 November 2010 22:39:31 Rafa? Mi?ecki wrote:
>> Daniel: anything new on this? Could you put that card in some "normal"
>> machine where it's relatively easy to install deubgging symbols?
> I'm afraid no. My wireless router is the only machine in my environment with a
> mini-PCI slot.
>
> I could however compile the kernel for my OpenWRT box with debugging symbols
> (KERNEL_DEBUG_INFO in OpenWRT config), if this helps.
Would be nice. I was afraid compiling kernel for OpenWRT won't be easy/fast.
> Could the PCI vendor id alone be the reason for this problem? As I mentioned
> earlier I've added the ID to b43_pci_bridge.c, but I am not sure whether this
> is sufficient or not.
Really, hard to say. dmesg with debugging symbold would at least give
some info what's going on.
--
Rafa?
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-11-17 23:10 ` Rafał Miłecki
@ 2010-11-17 23:23 ` Larry Finger
2010-11-19 17:26 ` Daniel Klaffenbach
1 sibling, 0 replies; 10+ messages in thread
From: Larry Finger @ 2010-11-17 23:23 UTC (permalink / raw)
To: b43-dev
On 11/17/2010 05:10 PM, Rafa? Mi?ecki wrote:
> W dniu 17 listopada 2010 23:48 u?ytkownik Daniel Klaffenbach
> <danielklaffenbach@gmail.com> napisa?:
>> On Wednesday 17 November 2010 22:39:31 Rafa? Mi?ecki wrote:
>>> Daniel: anything new on this? Could you put that card in some "normal"
>>> machine where it's relatively easy to install deubgging symbols?
>> I'm afraid no. My wireless router is the only machine in my environment with a
>> mini-PCI slot.
>>
>> I could however compile the kernel for my OpenWRT box with debugging symbols
>> (KERNEL_DEBUG_INFO in OpenWRT config), if this helps.
>
> Would be nice. I was afraid compiling kernel for OpenWRT won't be easy/fast.
>
>
>> Could the PCI vendor id alone be the reason for this problem? As I mentioned
>> earlier I've added the ID to b43_pci_bridge.c, but I am not sure whether this
>> is sufficient or not.
>
> Really, hard to say. dmesg with debugging symbold would at least give
> some info what's going on.
As the driver never loaded until you changed the vendor id, one could say that
your change "caused" the problem, but the data error you saw is likely due to an
attempt to read or write an address that is not properly mapped. There are too
many possibilities to speculate.
Larry
^ permalink raw reply [flat|nested] 10+ messages in thread
* BCM4318KFBG not recognized by b43
2010-11-17 23:10 ` Rafał Miłecki
2010-11-17 23:23 ` Larry Finger
@ 2010-11-19 17:26 ` Daniel Klaffenbach
1 sibling, 0 replies; 10+ messages in thread
From: Daniel Klaffenbach @ 2010-11-19 17:26 UTC (permalink / raw)
To: b43-dev
Hi,
On Thursday 18 November 2010 00:10:23 Rafa? Mi?ecki wrote:
> Would be nice. I was afraid compiling kernel for OpenWRT won't be
> easy/fast.
I've recompiled the latest OpenWRT trunk. I did turn on debugging symbols and
I've also applied the patch I did send earlier and to my surprise the module
loded without any complaints. dmesg gave me the following message:
b43-phy0: Broadcom 4318 WLAN found (core revision 9)
ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
Registered led device: b43-phy0::tx
Registered led device: b43-phy0::rx
Registered led device: b43-phy0::radio
Broadcom 43xx driver loaded [ Features: PL, GPIO LED Mask: 0x000f,
Firmware-ID: FW13 ]
b43 ssb1:0: firmware: requesting b43/ucode5.fw
b43 ssb1:0: firmware: requesting b43/pcm5.fw
b43 ssb1:0: firmware: requesting b43/b0g0initvals5.fw
b43 ssb1:0: firmware: requesting b43/b0g0bsinitvals5.fw
b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)
After doing some basic testing I can confirm that the card is working! I do not
know why it did give me the errors the last time, but I also did a nvram reset
of the box today - maybe that did the trick.
It would be nice if you could review my changes to
drivers/ssb/b43_pci_bridge.c and include/linux/pci_ids.h and add the vendor id
upstream.
Regards,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20101119/3ee0c1d3/attachment.sig>
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2010-11-19 17:26 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-10-20 19:28 BCM4318KFBG not recognized by b43 Daniel Klaffenbach
2010-10-20 21:21 ` Gábor Stefanik
2010-10-20 22:43 ` Daniel Klaffenbach
2010-10-22 9:15 ` Daniel Klaffenbach
2010-10-22 20:16 ` Larry Finger
2010-11-17 21:39 ` Rafał Miłecki
2010-11-17 22:48 ` Daniel Klaffenbach
2010-11-17 23:10 ` Rafał Miłecki
2010-11-17 23:23 ` Larry Finger
2010-11-19 17:26 ` Daniel Klaffenbach
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).