2009/6/12 Larry Finger <Larry.Finger@xxxxxxxxxxxx>: > 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@xxxxxxxxxxxxxxx > > Have you tested this boot parameter? > 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. I had tested this boot parameter, and it did not work better, so I did not notify linux-acpi@xxxxxxxxxxxxxxxx > 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 I am very familiar with this output, I have been getting this for years, related to the PCI express hardware; however ndiswrapper has no problem with the resource allocation or hardware. It works fine. > 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 > 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? Hey, I found an updated BIOS available in the HP site, obviously requiring Windows. I had deleted those partitions, so I will get a Windows hard disk/CD and try to flash it. I did not work under Wine... I will keep you informed. By the way, what is BAR? -- Fabio Andrés Correa Durán http://facorread.150m.com -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
