Brocade 1010/1020 10Gb Ethernet cards ( (Initiator, NIC Support)

[Roger Sterchi]

Should the Brocade 1010/1020 10Gb Ethernet cards still be supported as initiators (NIC Support).

Cause the module bna seams not to be included in /lib/modules/3.14.36-esos.prod/modules.dep.

Thanks,

Roger

[Marc Smith]

Hi Roger,

Its built-in to the kernel, not a module:
$ cat misc/linux-3.14.36.config | grep -i bna
CONFIG_BNA=y

Are cards not working in ESOS, or did I just miss adding these to the
supported-hardware wiki page?


--Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Roger Sterchi]

Hi Marc

The BR-1020 card don't work in my system. The card has the FW 3.2.5.0 installed. Should I downgrade the FW to 3.2.3.0?

During boot into debug mode, I get the following messages at the console:

[   92.988117] Can't locate firmware ctfw-3.2.3.0.bin

[   92.988526] Failed to load Firmware Image!

[   92.988920| bnad_pci_probe : (0xffff88041d75a888, 0xffffffff81a85d78) PCI Func : (3)

[   92.981711] bna 0000:06:00.3: Direct firmware load failed with error -2

[   92.982182] bna 0000:06:00.3: Falling back to user helper

# lspci -v

...

06:00.0 Fibre Channel: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA (rev 01)

        Subsystem: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA - FCOE

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at fe1c0000 (64-bit, non-prefetchable) [size=256K]

        Memory at fe20c000 (64-bit, non-prefetchable) [size=16K]

        Expansion ROM at fe000000 [disabled] [size=1M]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] MSI-X: Enable- Count=256 Masked-

        Capabilities: [60] Express Endpoint, MSI 00

        Capabilities: [a0] Vital Product Data

        Capabilities: [100] Advanced Error Reporting

        Capabilities: [140] Virtual Channel

        Capabilities: [180] Power Budgeting <?>

        Capabilities: [190] Alternative Routing-ID Interpretation (ARI)

06:00.1 Fibre Channel: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA (rev 01)

        Subsystem: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA - FCOE

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at fe180000 (64-bit, non-prefetchable) [size=256K]

        Memory at fe208000 (64-bit, non-prefetchable) [size=16K]

        Expansion ROM at fdf00000 [disabled] [size=1M]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] MSI-X: Enable- Count=256 Masked-

        Capabilities: [60] Express Endpoint, MSI 00

        Capabilities: [a0] Vital Product Data

        Capabilities: [100] Advanced Error Reporting

        Capabilities: [180] Power Budgeting <?>

        Capabilities: [190] Alternative Routing-ID Interpretation (ARI)

06:00.2 Ethernet controller: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA (rev 01)

        Subsystem: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA - LL

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at fe140000 (64-bit, non-prefetchable) [size=256K]

        Memory at fe204000 (64-bit, non-prefetchable) [size=16K]

        Expansion ROM at fde00000 [disabled] [size=1M]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] MSI-X: Enable- Count=256 Masked-

        Capabilities: [60] Express Endpoint, MSI 00

        Capabilities: [a0] Vital Product Data

        Capabilities: [100] Advanced Error Reporting

        Capabilities: [180] Power Budgeting <?>

        Capabilities: [190] Alternative Routing-ID Interpretation (ARI)

06:00.3 Ethernet controller: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA (rev 01)

        Subsystem: Brocade Communications Systems, Inc. 1010/1020/1007/1741 10Gbps CNA - LL

        Flags: bus master, fast devsel, latency 0, IRQ 10

        Memory at fe100000 (64-bit, non-prefetchable) [size=256K]

        Memory at fe200000 (64-bit, non-prefetchable) [size=16K]

        Expansion ROM at fdd00000 [disabled] [size=1M]

        Capabilities: [40] Power Management version 3

        Capabilities: [50] MSI-X: Enable- Count=256 Masked-

        Capabilities: [60] Express Endpoint, MSI 00

        Capabilities: [a0] Vital Product Data

        Capabilities: [100] Advanced Error Reporting

        Capabilities: [180] Power Budgeting <?>

        Capabilities: [190] Alternative Routing-ID Interpretation (ARI)

...

[Roger Sterchi]

The same problem with missing firmware file ctfw-3.2.3.0.bin after FW downgrade do V. 3.2.3.0 on BR-1020, but I found the file on a CentOS7 system. Where should I copy this file on ESOS?

[Marc Smith]

Hmm... 90 seconds into boot, so I wonder if its not attempting to load
firmware until the interfaces are brought up in rc.network... if so,
that's good for us, since that driver is built-in to the kernel and
not a module.

The "ctfw-3.2.3.0.bin" file comes from the linux-firmware package...
it belongs in /lib/firmware. I checked and we don't install that
particular firmware blob at this time... can you try the attached file
and put it into /lib/firmware on your ESOS host and let me know.

Actually do "mount /mnt/root" first and put it (the binary blob /
firmware file) into "/mnt/root/lib/firmware" then "umount /mnt/root"
and reboot.

Let me know if this fixes it and I'll push the change to master and 0.1.x.


--Marc

[Roger Sterchi]

I've just placed the file ctfw-3.2.3.0.bin in the directory /lib/firmware.

After a reboot, the system sill throughs to message: Can't locate firmware ctfw-3.2.3.0.bin.

I also tried to move the ctfw-3.2.3.0.bin in to the directory /lib/firmware/qlogic, with the same result.

[Roger Sterchi]

The following procedure also didn't work, the system sill throughs to message: Can't locate firmware ctfw-3.2.3.0.bin.

....

mount /mnt/root

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ctfw-3.2.3.0.bin

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ct2fw-3.2.3.0.bin

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/cbfw-3.2.3.0.bin

cp ctfw-3.2.3.0.bin /mnt/root/lib/firmware/

cp ct2fw-3.2.3.0.bin /mnt/root/lib/firmware/

cp cbfw-3.2.3.0.bin /mnt/root/lib/firmware/

cd /mnt/root/lib/firmware

ln -s ctfw-3.2.3.0.bin ctfw.bin

ln -s ct2fw-3.2.3.0.bin ct2fw.bin

ln -s cbfw-3.2.3.0.bin cbfw.bin

umount /mnt/root

init 6

[Marc Smith]

Hi Roger,

Can you do the following:
dmesg > /tmp/dmesg.out

Then attach that dmesg.out file to this thread or the contents of it.
I want to know at what point its looking for the firmware file...
maybe its not when bringing up the interface like I had assumed.

Also, not sure if I caught what version of ESOS you're using?


--Marc

[Roger Sterchi]

Hi Marc

I'm using esos--0.1.2.

In die mean time I'did some further testing.

The message "Can't locate firmware ctfw-3.2.3.0.bin" shows up during the init boot process via initramfs.

With the FW v3.2.3 loaded onto the card, I integrated fw files v3.2.3.0 into the initramfs.cpio.gz. Now the Brocade 10G Ethernet driver - version 3.2.23.0 loaded during the init boot. But a fraction of a sec. later the system freeze occurred.

I upgrade the FW of the card to v3.2.5.0 and integrated the recent fw files v3.2.5.1 into initramfs.cpio.gz, with the same freezing behaviour.

Here the steps I've taken to integrate the fw v3.2.5.1 files into the initramfs.cpio.gz:

mount /boot

cd /boot

gunzip initramfs.cpio.gz

mkdir tmp

cd tmp

cpio -id < ../initramfs.cpio

mkdir lib/firmware -p

cd ./tmp/firmware/

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ctfw-3.2.5.1.bin

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/ct2fw-3.2.5.1.bin

wget http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/cbfw-3.2.5.1.bin

ln -s ctfw-3.2.5.1.bin ctfw-3.2.3.0.bin

ln -s ct2fw-3.2.5.1.bin ct2fw-3.2.3.0.bin

ln -s cbfw-3.2.5.1.bin cbfw-3.2.3.0.bin

cd ../../

find . | cpio --create --format='newc' > ../initramfs.cpio

cd ..

gzip initramfs.cpio

rm ./tmp/ -fr

[Marc Smith]

Hi Roger,

Thanks for the information and testing. Can you post the output from
dmesg? It sounds like its needing the firmware before bringing up the
interface, but I'd like to confirm that. If that's the case, we can
simply make that driver into a module and load it during the init/rc
process... we already do this for several other drivers that rely on
these binary blobs.


--Marc

[Roger Sterchi]

Hi Marc

Find attached the dmesg output.