Opened 14 years ago

Closed 10 years ago

#6534 closed bug (fixed)

Broadcom bcm43xx pci id 0x4311 not supported

Reported by: saivert Owned by: axeld
Priority: normal Milestone: R1
Component: Network & Internet/Wireless Version: R1/Development
Keywords: bcm43xx 0x4311 Cc:
Blocked By: Blocking: #8045
Platform: All

Description

Listdev output:

device Network controller [2|80|0]
  vendor 14e4: Broadcom Corporation
  device 4311: BCM4311 802.11b/g WLAN

syslog snippet:

KERN: broadcom43xx: init_driver(0x83f03468)
KERN: [broadcom43xx] (bwi) bus_alloc_resource(3, [16], 0x0, 0xffffffff, 0x1,0x2)
KERN: add_memory_type_range(1652, 0xd0000000, 0x20000, 0)
KERN: set MTRRs to:
KERN:   mtrr:  0: base: 0x3f680000, size:    0x80000, type: 0
KERN:   mtrr:  1: base: 0xd0000000, size: 0x10000000, type: 0
KERN:   mtrr:  2: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  3: base: 0x80000000, size: 0x80000000, type: 1
KERN: [broadcom43xx] (bwi) bus_alloc_resource(1, [0], 0x0, 0xffffffff, 0x1,0x6)
KERN: [broadcom43xx] (bwi) no BBP id for device id 0x4311

Change History (14)

comment:1 by korli, 13 years ago

Could you please check with hrev41559 or newer on trunk?

comment:2 by saivert, 13 years ago

Still not working. same laptop as before.

comment:3 by korli, 13 years ago

It seems the trunk bwi driver in FreeBSD doesn't support this revision either. First two numbers of the following array are the supported ranges.

{ 0x4301, 0x4301, 0x4301 },
{ 0x4305, 0x4307, 0x4307 },
{ 0x4403, 0x4403, 0x4402 },
{ 0x4610, 0x4615, 0x4610 },
{ 0x4710, 0x4715, 0x4710 },
{ 0x4720, 0x4725, 0x4309 } 

comment:5 by Hubert, 12 years ago

I have similar problem with 4312:

device Network controller [2|80|0]
  vendor 14e4: Broadcom Corporation
  device 4315: BCM4312 802.11b/g LP-PHY

KERN: PCI:   Capabilities: PCIe, MSI, subvendor, PM
KERN: PCI: [dom 0, bus 16] bus  16, device  0, function  0: vendor 14e4, device 4315, revision 01
KERN: PCI:   class_base 02, class_function 80, class_api 00
KERN: PCI:   vendor 14e4: Broadcom Corporation
KERN: PCI:   device 4315: BCM4312 802.11b/g LP-PHY (BCM4312 802.11b/g Wireless LAN Controller)
KERN: PCI:   info: Network controller
KERN: PCI:   line_size 10, latency 00, header_type 00KERN: , BIST 00
KERN: PCI:   ROM base host 00000000, pci 00000000, size 00000000
KERN: PCI:   cardbus_CIS 00000000, subsystem_id 137d, subsystem_vendor_id 103c
KERN: PCI:   interrupt_line 0a, interrupt_pin 01, min_grant 00, max_latency 00
KERN: PCI:   base reg 0: host e4000000, pci e4000000, size 00004000, flags 04
KERN: PCI:   base reg 1: host 00000000, pci 00000000, size 00000010, flags 0f
KERN: PCI:   base reg 2: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 3: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 4: host 00000000, pci 00000000, size 00000000, flags 00
KERN: PCI:   base reg 5: host 00000000, pci 00000000, size 00000000, flags 00}}}



I not see this broadcom in Network Preferences - ofcourse before I installed firmware
Version 1, edited 12 years ago by Hubert (previous) (next) (diff)

comment:6 by taos, 12 years ago

I'm not really sure, but bcm4312 might be supported by bwn in FreeBSD (9-current). From FreeBSD bwn(4) man page:

The bwn driver supports Broadcom BCM43xx based wireless devices, including:

Card             Chip       Bus   Standard

[...]
HP Compaq 6715b  BCM4312    PCI   b/g
[...]

I was looking for support of bcm43225 - no luck so far.

comment:7 by modeenf, 12 years ago

You have so right. Was not if_bwi.c in FreeBSD but if_bwi_pci.c that had the information

{ PCI_VENDOR_BROADCOM, 0x4301,"Broadcom BCM4301 802.11b Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4307,"Broadcom BCM4307 802.11b Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4311,"Broadcom BCM4311 802.11b/g Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4312,"Broadcom BCM4312 802.11a/b/g Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4313,"Broadcom BCM4312 802.11a Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4320,"Broadcom BCM4306 802.11b/g Wireless Lan"}, { PCI_VENDOR_BROADCOM, 0x4321,"Broadcom BCM4306 802.11a Wireless Lan"}, { PCI_VENDOR_BROADCOM, 0x4325,"Broadcom BCM4306 802.11b/g Wireless Lan"}, { PCI_VENDOR_BROADCOM, 0x4324,"Broadcom BCM4309 802.11a/b/g Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4318,"Broadcom BCM4318 802.11b/g Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x4319,"Broadcom BCM4318 802.11a/b/g Wireless Lan" }, { PCI_VENDOR_BROADCOM, 0x431a,"Broadcom BCM4318 802.11a Wireless Lan" },

comment:8 by diver, 12 years ago

Blocking: 8045 added

comment:9 by korli, 11 years ago

Please test with a current revision.

comment:10 by marcm, 11 years ago

tested with hrev45986 and installed wifi fw

bcm4312 doesn't show up in /dev/net

comment:11 by korli, 11 years ago

Please provide a syslog.

comment:12 by marcm, 11 years ago

Here it is:

KERN: PCI: class_base 02, class_function 80, class_api 00 KERN: PCI: vendor 14e4: Broadcom Corporation KERN: PCI: device 4315: BCM4312 802.11b/g LP-PHY KERN: PCI: info: Network controller KERN: PCI: line_size 10, latency 00, header_type 00, BIST 00 KERN: PCI: ROM base host 00000000, pci 00000000, size 00000000 KERN: PCI: cardbus_CIS 00000000, subsystem_id 04b5, subsystem_vendor_id 14e4 KERN: PCI: interrupt_line 03, interrupt_pin 01, min_grant 00, max_latency 00 KERN: PCI: base reg 0: host f4500000, pci f4500000, size 00004000, flags 04 KERN: PCI: base reg 1: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 2: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 3: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 4: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: base reg 5: host 00000000, pci 00000000, size 00000000, flags 00 KERN: PCI: Capabilities: PM, vendspec, MSI, PCIe KERN: PCI: Extended capabilities: Advanced Error Reporting, Virtual Channel, Serial Number, Power Budgeting

Any hope it will be supported in the near future?

comment:13 by korli, 11 years ago

@marcm it seems this device isn't supported by bwi but by bwn, which isn't ported yet. Furthermore it needs another module siba_bwn, which might need more work like other drivers. In anycase this deserves a new enhancement ticket.

comment:14 by luroh, 10 years ago

Resolution: fixed
Status: newclosed

Likely fixed and closing it as such, despite the lack of feedback. Hubert, marcm: Please open a separate enhancement ticket for your device if needed.

Note: See TracTickets for help on using tickets.