Re: 4311 not detected at all

Re: 4311 not detected at all

[Larry Finger]

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

Re: 4311 not detected at all

[Fabio A. Correa]

2009/6/12 Larry Finger <Larry.Finger@lwfinger.net>:
> 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?
> 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@vger.kernel.org.

> 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

Re: 4311 not detected at all

[Larry Finger]

Fabio A. Correa wrote:
> 
> 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?

Base Address Register

Re: 4311 not detected at all

[Larry Finger]

Fabio A. Correa wrote:
> 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.

If you have access to a running Windows XP system on another computer,
there is a way to build a Windows Live CD from which to run your BIOS
update. Download the Bart's PE file (http://www.nu2.nu/pebuilder/) and
install it. Run it with a Windows distribution CD mounted.

If you have the Windows CD, but not access to a machine running
Windows, the .iso can be built in a virtual machine. I used a
VirtualBox copy of Windows XP. Unfortunately, the builder will not run
in Wine.


Larry

Re: 4311 not detected at all

[Gábor Stefanik]

On Sat, Jun 13, 2009 at 1:35 AM, Larry Finger<Larry.Finger@lwfinger.net> wrote:
> Fabio A. Correa wrote:
>> 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.
>
> If you have access to a running Windows XP system on another computer,
> there is a way to build a Windows Live CD from which to run your BIOS
> update. Download the Bart's PE file (http://www.nu2.nu/pebuilder/) and
> install it. Run it with a Windows distribution CD mounted.
>
> If you have the Windows CD, but not access to a machine running
> Windows, the .iso can be built in a virtual machine. I used a
> VirtualBox copy of Windows XP. Unfortunately, the builder will not run
> in Wine.

Alternatively, you can use a Windows Vista/Windows 7 RC setup DVD as
is, unmodified. (Use the recovery environment.)

-- 
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)

Re: 4311 not detected at all

[Fabio A. Correa]

After days of failure, I resorted to ndiswrapper-1.54, which installed
without trouble.

--
Fabio Andrés Correa Durán

Re: 4311 not detected at all

[Fabio A. Correa]

OK, I found new data on my problem, this might shed light on some
fix/enhancement for the driver.

When the system starts, the iomem of the 4311 card is specified to be
pci 0000:06:00.0: reg 10 32bit mmio: [0xd0000000-0xd0003fff]

The iomem of 4311 cannot be allocated:
arch/x86/pci/i386.c:173: pci 0000:06:00.0: BAR 0: can't allocate resource

the next two instructions of file i386.c mean that the iomem range
converts from 0xd0000000-0xd0003fff to 0x000000-0x003fff. Then
b43-pci-bridge tries to allocate this iomem resource, which is
invalid:
drivers/pci/setup-res.c:290: b43-pci-bridge 0000:06:00.0: device not
available because of BAR 0 [0x000000-0x003fff] collisions
drivers/base/dd.c:143: b43-pci-bridge: probe of 0000:06:00.0 failed
with error -22

The 4311 card (06:00.0) is in the PCI Express port 00:1c.2, with
resources that are reported later:
pci 0000:00:1c.2: PCI bridge, secondary bus 0000:06
pci 0000:00:1c.2:   MEM window: 0x88000000-0x880fffff

After booting, lspci -vvv shows:

00:1c.2 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express
Port 3 (rev 01) (prog-if 00 [Normal decode])
        Memory behind bridge: 88000000-880fffff
06:00.0 Network controller: Broadcom Corporation BCM4311 802.11b/g WLAN (rev 01)
        Region 0: Memory at 88000000 (32-bit, non-prefetchable)
[size=16K]

16K = 3fff.

Well then; the b43 controller stops probing my 4311 card because the
wrong resource is probed for.

I am not sure who should I direct this message to.

-- 
Fabio Andrés Correa Durán

Re: 4311 not detected at all

[Peter Stuge]

Fabio A. Correa wrote:
> > 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.

You may be able to use flashrom as developed by the coreboot project
to flash your BIOS. Maybe. If not, come on IRC or the mailing list
and we can try to help you get it to work on your laptop.

http://coreboot.org/Flashrom
http://coreboot.org/IRC
http://coreboot.org/Mailinglist


> By the way, what is BAR?

The boot firmware (usually BIOS) assigns PCI devices an address range
through which software can exchange data with the device. Each device
specifies the size for it's address ranges, the firmware calculates
how all ranges fit together, and then writes the start, or base,
address to the respective BAR in each device.

The addresses are the same as RAM addresses, which is why 32-bit
systems can not use full 4GB of RAM. The PCI device address ranges
will occupy the last part of memory space.

Better BAR allocation algorithms could allow more usable RAM, but it
also depends on chipset limitations.


//Peter

Re: 4311 not detected at all

[Fabio A. Correa]

2009/6/17 Peter Stuge <peter@stuge.se>:
> You may be able to use flashrom as developed by the coreboot project
> to flash your BIOS. Maybe. If not, come on IRC or the mailing list
> and we can try to help you get it to work on your laptop.

Thank you very much. I emerged it on my Gentoo laptop and the BIOS was
detected, but:

Found chipset "Intel ICH7M", enabling flash write...
BIOS Lock Enable: disabled, BIOS Write Enable: disabled, BIOS_CNTL is
0x0

Root Complex Register Block address = 0xfed1c000
GCS = 0xc60: BIOS Interface Lock-Down: disabled, BOOT BIOS Straps: 0x3 (LPC)
Top Swap : not enabled

The BIOS could not be read into a file, so I will not try to write it.
Anyways, thanks for your help.

-- 
Fabio Andrés Correa Durán

Re: 4311 not detected at all

[Peter Stuge]

Fabio A. Correa wrote:
> > You may be able to use flashrom as developed by the coreboot project
> > to flash your BIOS. Maybe. If not, come on IRC or the mailing list
> > and we can try to help you get it to work on your laptop.
> 
> Thank you very much. I emerged it on my Gentoo laptop and the BIOS
> was detected, but:

Please let's move this to a better discussion forum. IRC would be best
for trying to make this work, I think it can work because the BIOS
flashing protection that can be enabled in your chipset does not seem
to be active.

At the very least we need the full output from a run of flashrom -V,
but let's continue the discussion either on IRC (would be best) or on
the coreboot mailing list.

Thanks!


//Peter

Re: 4311 not detected at all

[Fabio A. Correa]

Hello All,

I recompiled the Linux kernel with ssb, phy and b43 as modules. I made
sure those modules were loaded after login, and now the b43 driver
properly detects the card. It seems the phy driver is not needed.

Now I have the problem that the card does not scan, and it does not
associate to any AP.

-- 
Fabio Andrés Correa Durán
http://facorread.150m.com

Re: 4311 not detected at all

[Larry Finger]

Fabio A. Correa wrote:
> Hello All,
> 
> I recompiled the Linux kernel with ssb, phy and b43 as modules. I made
> sure those modules were loaded after login, and now the b43 driver
> properly detects the card. It seems the phy driver is not needed.
> 
> Now I have the problem that the card does not scan, and it does not
> associate to any AP.

AFAIK, the phy driver is for wired devices. Have you installed the
firmware? Please look at the output of the command

dmesg | egrep "ssb|b43|wlan0"

The other kernel modules that are needed are mac80211 and friends;
however, the Kconfig rules should ensure that mac80211 is built before
you can actually build b43.

BTW, your mailer is misconfigured. the "To:" header field is wrong,
which prevents an automatic "reply to".