366T - Unable to upgrade firmware under Linux (1.27.30)

[rcstevensonaz]

(please let me know if this should be posted to a different forum section)

Any insight on (a) why the firmware upgrade is failing, even though the discovery step does correctly find the device, (b) whether I can / should force upgrade of the firmware to latest from HPE, or (c) use the Intel-provided firmware update insted? 

I am running into issue upgrading the firmware to 1.27.30 on a recently acquired used HPE 366T ethernet adapter (HPE 811546-B21 || Intel i350T4v2 OEM).  Using Debian 11.5. Motherboard is SuperMicro MBD-X10SLM+-LN4F, which has built in 4-port Intel I210 NIC.

Result of running the ./setup command from downloaded file firmware-nic-intel-1.27.30-1.1.x86_64.rpm:

root@debian-usb:/usr/lib/x86_64-linux-gnu/firmware-nic-intel-1.27.30-1.1# ./setup
Copyright (c) 2023 Hewlett Packard Enterprise Development LP

HPE Intel Online Firmware Upgrade Utility for Linux x86_64 - v1.27.30

The discovery operation has failed
Can't find supported devices in the system!

 Copy of log data from /var/cpq/CP056063.log

================================================================
Copyright (c) 2023 Hewlett Packard Enterprise Development LP
HPE Intel Online Firmware Upgrade Utility for Linux x86_64
================================================================

Installation started: [Sun Apr 30 22:45:42 2023]

Installing: CP056063.scexe
Version: 1.27.30

OS: Debian GNU/Linux 11 (bullseye)
Kernel Release: 5.10.0-22-amd64
Driver Info: igb-
Adapters: "HP Ethernet 1Gb 4-port 366T Adapter";

Command: ./.setup

[ERROR] The discovery operation has failed
[ERROR] The return code for the second oem_get_adapter_info() call: 4

[ERROR] Can't find supported devices in the system!

Return Value: FWUPG_NOOP [3]

Installation complete: [Sun Apr 30 22:45:50 2023]
================================================================

Output from running discovery script command  ./hpsetup -d /home/craig/discovery.log

Copyright (c) 2023 Hewlett Packard Enterprise Development LP
HPE Intel Online Firmware Upgrade Utility for Linux x86_64 - v1.27.30

The discovery XML is created at the location: /home/craig/discovery.log
The 'discover' (oem_do_discovery_with_files) operation was successful

Contents of the discovery file /home/craig/discovery.log

<?xml version="1.0" encoding="UTF-8"?>
<hp_rom_discovery version="2.0.0.0">
        <type value=""/>
        <alt_name value="HPE Online Firmware Upgrade Utility for Linux x86_64"/>
        <version value="1.27.30"/>
        <takes_effect value="deferred"/>
        <devices>
                <device>
                        <product_id value="HPE Ethernet 1Gb 4-port 366T Adapter"/>
                        <venid value="8086"/>
                        <devid value="1521"/>
                        <subvenid value="103C"/>
                        <subdevid value="8157"/>
                        <segment value="0000"/>
                        <busnumber value="06"/>
                        <devicenumber value="00"/>
                        <funcnumber value="00"/>
                        <device_id value=""/>
                        <macaddress value=""/>
                        <slotnumber value="FFFFFFFF"/>
                        <nictype value="INTEL_1GB_NIC"/>
                        <fw_item>
                           <type value="NVM"/>
                           <firmware_id value=""/>
                           <firmware_file value=""/>
                           <version value="0.0.00000000"/>
                           <active_version value="0.0.00000000"/>
                           <action value="skip"/>
                           <duration value=""/>
                           <message value="Adapter initialization failed. Attempt to update the firmware will fail, so update operation will be skipped."/>
                           <shared value="no"/>
                        </fw_item>
                </device>
        </devices>
</hp_rom_discovery>

Output from the Linux command lshw, showing only the result of the first of four ports: lshw -class network

  *-network:0
       description: Ethernet interface
       product: I350 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:06:00.0
       logical name: enp6s0f0
       version: 01
       serial: 48:df:37:xx:xx:xx
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress vpd bus_master cap_list rom ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=5.10.0-22-amd64 duplex=full firmware=1.52, 0x80000f42, 1.1446.0 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:19 memory:e0600000-e06fffff memory:e0c00000-e0c03fff memory:e0a00000-e0a7ffff memory:e0c04000-e0c23fff memory:e0c24000-e0c43fff

Listing of all NICs in the machine (and showing that all 366T ports are UP), from command ip -a:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 0c:c4:7a:xx:xx:xx brd ff:ff:ff:ff:ff:ff
    altname enp4s0
    inet 10.10.4.205/24 brd 10.10.4.255 scope global dynamic noprefixroute eno1
       valid_lft 593sec preferred_lft 593sec
    inet6 fe80::ec4:7aff:fe74:b898/64 scope link noprefixroute
       valid_lft forever preferred_lft forever
3: eno2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 0c:c4:7a::xx:xx:xx brd ff:ff:ff:ff:ff:ff
    altname enp5s0
4: enp6s0f0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:df:37::xx:xx:xx brd ff:ff:ff:ff:ff:ff
5: enp6s0f1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:df:37::xx:xx:xx brd ff:ff:ff:ff:ff:ff
6: enp6s0f2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:df:37::xx:xx:xx brd ff:ff:ff:ff:ff:ff
7: enp6s0f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 48:df:37::xx:xx:xx brd ff:ff:ff:ff:ff:ff
8: eno3: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 0c:c4:7a::xx:xx:xx brd ff:ff:ff:ff:ff:ff
    altname enp7s0
9: eno4: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether 0c:c4:7a::xx:xx:xx brd ff:ff:ff:ff:ff:ff
    altname enp8s0

[Vinky_99]

@rcstevensonaz

Hello, 

This can be due to various reasons, such as a compatibility issue between the firmware upgrade utility and the Linux distribution or the adapter's firmware.

As for whether you should force upgrade the firmware to the latest from HPE or use the Intel-provided firmware update, it depends on your specific requirements and the compatibility of the firmware with your adapter. In general, it is recommended to use the firmware provided by the adapter's manufacturer, which is HPE in this case. However, you should make sure that the firmware is compatible with your adapter and the Linux distribution.

To troubleshoot the firmware upgrade issue, you can try the following steps:

1. Check if the required dependencies for the firmware upgrade utility are installed on your system.

2. Make sure that the adapter is properly installed and recognized by the operating system.

3. Check if there are any conflicts with other network devices or drivers.

4. Try upgrading the firmware using a different version of the firmware upgrade utility.
   
   I hope this helps! Best of Luck

[Kashyap02]

Hi, 

We have installed this version on our lab server, which works fine without any issues. 
I OS on the lab server was RHEL. As @Vinky_99 said, there could be dependencies as you are using a different flavor or the Linux distribution. 
Check the dependencies, or try other versions. 

[rcstevensonaz]

I have no doubt that software itself runs under the very limited set of OSs that HPE claims (e.g., RHEL), using a card that is known good and in a known state.  But, that isn't my environment.

I am running a clean install of Debian 11, fully up to date. When I try to run prior version of the firmware upgrade, it is able to articulate the card and the ethernet ports; but then goes on to give a HW segmentation fault. If there are further dependencies for Linux Debian beyond the igb driver, they are not documentated anywhere and do not show up when I install the RPM (using alien) .

I am curious about the firwmare version on this card , via "ethtool -i enp6s0f0 0": firmware=1.52, 0x80000f42, 1.1446.0

The 1.1446.0 matches with firmware releases 1.11.12 (Nov 7, 2016) or 1.11.13 (Jan, 2017).  But the release notes for 366T indicate an EEPROM/NVM Version of 0x80000DC6; and the 1Gb boot code as v1.5.72.

[Kashyap02]

Hi, 

Try to do a clean installation. Remove the current firmware package and install the latest available on the NIC. 
you can also use the command dpkg -i <Package name> to find out the dependencies. 

[Sunitha_Mod]

Hello @rcstevensonaz,

Let us know if you were able to resolve the issue.

If you have no further query and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.