Re: 4311 not detected at all

[Larry Finger <Larry.Finger@lwfinger.net>]

Fabio A. Correa wrote:
> Hello there, you are a great team and I thank you for bringing this
> excellent piece of software to us. Keep the work up.
> 
> Given the features that you report in the source code, I am anxious to
> give it a try under linux-2.6.30. I have been working with ndiswrapper
> in the past, because bcm43xx did not fit my needs. I have compiled the
> 2.6.30 kernel tens of times with different settings for PHY, SSB and
> B43. However, PHY and SSB do not show signs of life and B43 only show
> its presentation line in the syslog.
> 
> Would you please help me find a cause for this silence? Thank you very much.

There are three areas in your dmesg output that attracted my attention:

ACPI: BIOS bug: multiple APIC/MADT found, using 0
ACPI: If "acpi_apic_instance=2" works better, notify
linux-acpi@vger.kernel.org

Have you tested this boot parameter?

Later there is this output:

pci 0000:00:1c.0: BAR 7: can't allocate resource
pci 0000:00:1c.0: BAR 8: can't allocate resource
pci 0000:00:1c.1: BAR 7: can't allocate resource
pci 0000:00:1c.1: BAR 8: can't allocate resource
pci 0000:00:1c.2: BAR 7: can't allocate resource
pci 0000:00:1c.2: BAR 8: can't allocate resource
pci 0000:06:00.0: BAR 0: can't allocate resource

and later:

b43-pci-bridge 0000:06:00.0: device not available because of BAR 0
[0x000000-0x003fff] collisions
b43-pci-bridge: probe of 0000:06:00.0 failed with error -22

So, the BAR problem is preventing ssb from loading, thus b43 cannot
function. If the "acpi_apic_instance=2" option does not fix the
problem, then you need to post this problem on the Linux Kernel
Mailing List.

The bottom line is that a BIOS error is likely the problem with BAR
allocation on your machine. Have you checked to see if an updated one
is available?

Larry