Proxmox user base seems rather thin?

keeka said:
As a newcomer to Linux and Linux-based virtualisation, your time might be better spent putting this network card issue aside for a while and sticking with PVE8. I have a similar network card in my setup, so was interested in your report. It's a common card so should surface again soon as more users upgrade and experienced users take an interest in it. But if it is associated with a specific and old hardware combination (motherboard?) you may be out of luck. I have winged it for a long time on old hardware but PVE9 may present some issues for me! I may be OK in this instance as I have not enables passthrough and your problem looks to be connected to IOMMU.
I have not come across another community forum where you'll find the same level engagement as you do from the staff here. This forum is an amazing resource. My only problem is using google these days to find the posts that help me.
Click to expand...

I didn't specifically enable passthrough, and I'm just a baby newcomer to Linux, so I don't know if passthrough is something that happens during install or not. Yet :). What is super weird is that the onboard NICs (two of the four anyway - the other two are x540, which is an issue I'll get to after this one is resolved) are recognized and functional, and I have to assume that they are being assigned address space, but the T4 is unable to reserve address space.

Don't feel alone in regard to google. It works, of course, but takes a lot of sifting. I've been using Grok and GPT-4 for searches, which returns source and synopsis.
 
tinus_p said:
Proxmox VE is built on Debian, chances are if there is a problem with the kernel and these network cards, it also appears on a stock Debian installation. Did you happen to check if they work if you run Debian 13 (could just try the live image)?

If not, you might be more successful in getting this fixed by reporting the issue to the Debian developers.
Click to expand...

Yep, they sure did work on Debian, but I'm going to reinstall it on another drive to test it out today. I'll post back what I find. I did see during my searching that it did crop up in Debian installs, but that was usually when someone was trying to passthrough to a VM. In this case, in this particular install, I haven't added any VMs.
 
leesteken said:
Proxmox's Linux kernel (6.14) is based on Ubuntu instead of Debian and since drivers come with the kernel, maybe try an Ubuntu (installer without installing it) with the same kernel version (25.04).
EDIT: The user-space is indeed based on Debian stable (13).
Click to expand...

I've also installed Ubuntu and Ubuntu server. Both saw all the NICs except the two x540 (also Intel and supposedly the same driver). Maybe I'll try all three again today.
 
mgibson said:
I don't have an intel NIC, but I see there are a number of posts on the forum that are about this card (here, here and here). Are you able to modify grub as in this post?
Click to expand...

I did read all of those a couple days ago. They seemed similar, but different in their own ways, with the possible exception of the Grub edit (which I haven't checked into yet). I do have them saved in my resource bookmarks so I can refer back to them though.
 
Isn't this a problem caused by a Bios glitch?

Isn't this a case where the range was allocated because it was recognized as usable, but in fact could not be used?

There was a patch that ignored the Bios defect and forced it to be usable, but of course it was not reflected in the normal kernel.

Is this different from this?

Don't rant just because you can't find a solution.

https://bugzilla.kernel.org/show_bug.cgi?id=218050
 
Last edited:
  • Like
Reactions: mike the newb and fba
uzumo said:
Isn't this a problem caused by a Bios glitch?

Isn't this a case where the range was allocated because it was recognized as usable, but in fact could not be used?

There was a patch that ignored the Bios defect and forced it to be usable, but of course it was not reflected in the normal kernel.

Is this different from this?

Don't rant just because you can't find a solution.

https://bugzilla.kernel.org/show_bug.cgi?id=218050
Click to expand...

The ixgbe is a different beast than the igb (i350), but interesting find that I hadn't seen yet. And it does relate to memory address space, but I don't think it's the issue here. On this motherboard, as on many, there is configurable memory allocation space set aside for pci. I installed a USB card, which was also addressed space in the same range. It did not overlap the i350, and worked fine. I pulled the i350 out and put the USB card in the same slot (just for grins) and it pulled the same address space the i350 had (since that was the beginning of pci space available), and it worked. So, the bios seems to be doing its job correctly.

As a further test, I pulled both cards, rebooted with them out, shut down, put in the i350, and it pulled the same address space as before. It didn't work and shows identical failures to before.

This shows the onboard NIC and the first NIC of the T4:

Code: 
root@PVE:/# lshw -C network
  *-network:0               
       description: Ethernet interface
       product: I350 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: eno1
       version: 01
       serial: 00:25:90:7c:2e:ea
       size: 1Gbit/s
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=igb driverversion=6.14.11-1-pve duplex=full firmware=1.52.0 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
       resources: irq:33 memory:fb920000-fb93ffff ioport:d020(size=32) memory:fb944000-fb947fff memory:fb948000-fb967fff memory:fb968000-fb987fff
      
      
      
       *-network:0 UNCLAIMED
       description: Ethernet controller
       product: I350 Gigabit Network Connection
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:07:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi msix pciexpress cap_list
       configuration: latency=0
       resources: memory:30000000-300fffff memory:30600000-30603fff memory:30400000-3047ffff memory:30604000-30623fff memory:30624000-30643fff
 
I have these NICs running for ages and atm. on 6.14.8-2-bpo12-pve

Flash firmware: https://calvin.me/how-to-update-intel-nic-firmware/ https://www.reddit.com/r/homelab/comments/eda5qp/updating_firmware_on_i350_t4/
20.4.1 mentioned there is old, very old. I do not know if firmware for the I350 is still available in the latest package, I think it went EOL some versions back from v30, but I don't know for sure. https://www.intel.com/content/www/u...t-utility-preboot-images-and-efi-drivers.html
Dig through the packages or readme if there is support/firmware. Choose then the latest for flashing and the "combo"-option. That means flashing parts for legacy machines and newer ones with UEFI. You need to flash every single port, so 4x.
With compatible UEFI-initialization your bar errors should be gone, regardless of the previous behaviour with older kernels.
If this doesn't help after flashing, try to switch off rebar/resizeable bar in BIOS or boot in CSM/legacy mode.
 
  • Like
Reactions: mike the newb
mr44er said:
I have these NICs running for ages and atm. on 6.14.8-2-bpo12-pve

Flash firmware: https://calvin.me/how-to-update-intel-nic-firmware/ https://www.reddit.com/r/homelab/comments/eda5qp/updating_firmware_on_i350_t4/
20.4.1 mentioned there is old, very old. I do not know if firmware for the I350 is still available in the latest package, I think it went EOL some versions back from v30, but I don't know for sure. https://www.intel.com/content/www/u...t-utility-preboot-images-and-efi-drivers.html
Dig through the packages or readme if there is support/firmware. Choose then the latest for flashing and the "combo"-option. That means flashing parts for legacy machines and newer ones with UEFI. You need to flash every single port, so 4x.
With compatible UEFI-initialization your bar errors should be gone, regardless of the previous behaviour with older kernels.
If this doesn't help after flashing, try to switch off rebar/resizeable bar in BIOS or boot in CSM/legacy mode.
Click to expand...

I'll try to work my way through that but, by way of analogy, you're a rocket scientist and I'm paddling a canoe :)
However, what is still very odd is that the onboard NICs are also i350, and they work fine. I'll post back after I follow your guidance here.
Thank you, BTW.
 
mike the newb said:
I'll try to work my way through that but, by way of analogy, you're a rocket scientist and I'm paddling a canoe :)
However, what is still very odd is that the onboard NICs are also i350, and they work fine. I'll post back after I follow your guidance here.
Thank you, BTW.
Click to expand...

Well, no luck trying to flash. I can't even get the EFI shell to work properly. in my case, this is the built in shell. If I try to map, I can only see half of the output, but the USB drive I'm using comes up as fs2, which I can't do anything with. It's a DOS bootable disk with the necessary files on it. As I said, I'm paddling a canoe.
 
Create a bootable FreeDOS flash drive with https://rufus.ie/en/
Switch your mobo-BIOS to boot legacy/CSM with it. (hammering F12 after start opens up boot override on some mainboards, could also be F9 or F11. if you see your drive 2x, then you choose the non-UEFI entry). If it boots to DOS-prompt, you're golden.

mike the newb said:
It's a DOS bootable disk with the necessary files on it
Click to expand...
Copy these files additionally onto the flash drive, then boot it. Ignore *.efi, flash the binary with the .exe
If it does not work, try it with an old spare PC, best if this doesn't have at all UEFI-Bios...but regardless of this, flash "combo".
 
  • Like
Reactions: mike the newb
mr44er said:
Create a bootable FreeDOS flash drive with https://rufus.ie/en/
Switch your mobo-BIOS to boot legacy/CSM with it. (hammering F12 after start opens up boot override on some mainboards, could also be F9 or F11. if you see your drive 2x, then you choose the non-UEFI entry). If it boots to DOS-prompt, you're golden.


Copy these files additionally onto the flash drive, then boot it. Ignore *.efi, flash the binary with the .exe
If it does not work, try it with an old spare PC, best if this doesn't have at all UEFI-Bios...but regardless of this, flash "combo".
Click to expand...

Gotcha, I thought it all had to be done from the EFI shell for some reason. I'll give it a shot.
 
mike the newb said:
Gotcha, I thought it all had to be done from the EFI shell for some reason. I'll give it a shot.
Click to expand...

Well, no go with that attempt as there is no DOS executable with the firmware update package, so I'm back to the EFI shell, which also renders me incapable of flashing the NIC.
Whether I fail to understand UEFI shell commands, or supermicro's UEFI shell structure is not so good, I have no ability (that I understand anyway) to flash the NICs in either way.
I have a non-intel based NIC coming tomorrow so I can do some more testing.

My (overall) guess is that the Intel i350 driver/kernel is having a hard time working with two separate NICs on different busses and assigning memory address space correctly.

In my case, there is abundant memory space available, and the server is a very simple bare-roots Proxmox install. As it's booting, I can see the address space assigned, with no errors, until it attempts to reserve the same memory it's already been assigned.

My canoe is now a floaty :)
For the time being anyway.
 
Kingneutron said:
Lots of us here are in tech-support related positions, so forum support gets to seem like "more work" after a while.
Click to expand...

Lots of new forum members (like me!) might be quite willing and able to help, and initially have some inclination to do so.
(And good people, especially when themselves need help, should be more inclined to "give back" too)
But absolutely agree its just unpaid work, especially when they (like me) work for / run an MSP, IT Dept, etc, etc.
That inclination to actively be helpful can fade rapidly.

Back in the IRC days, the phrase "Help Vampire" was coined (see https://slash7.com/2006/12/22/vampires/)
These people really suck the motivation/inclination to help out of a community!
 
  • Like
Reactions: Johannes S
Can you post your output from proxmox (onboard and your card, preferable from all 6 ports)? https://www.intel.com/content/www/us/en/support/articles/000059457/ethernet-products.html
My 4 on the NIC are the same:
Code: 
ethtool -i enp13s0f0
driver: igb
version: 6.14.8-2-bpo12-pve
firmware-version: 1.52, 0x00000000, 1.3256.0
expansion-rom-version:
bus-info: 0000:0d:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

It seems that the preboot package 26.6 from 10/18/2021 already kicked out files for the I350, I dig further. Maybe even older package is needed.
Anyway in the readme from 26.6:
1GbE Quad Port Server Adapter Notes
===================================

System does not boot
--------------------
Your system may run out of I/O resources and fail to boot if you install more
than four quad port server adapters. Moving the adapters to different slots or
rebalancing resources in the system BIOS may resolve the issue.
This issue affects the following Adapters:
* Intel(R) Ethernet Server Adapter I350-T4
Intel(R) Ethernet Desktop Adapter and Network Connection Notes
==============================================================
Click to expand...

Edit:
Grab the preboot_26.6.tar.gz, shovel it into proxmox.
Code: 
tar -xvf preboot_26.6.tar.gz
cd APPS/BootUtil/Linux_x64
chmod +x bootutil64e
./bootutil64e
Connection to QV driver failed - please reinstall it!

Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.37.28.0
Copyright (C) 2003-2021 Intel Corporation

Type BootUtil -? for help

Port Network Address Location Series  WOL Flash Firmware                Version
==== =============== ======== ======= === ============================= =======
  1   001999E3AEE6    13:00.0 Gigabit YES UEFI,PXE Enabled              1.5.89
  2   001999E3AEE7    13:00.1 Gigabit YES UEFI,PXE Enabled              1.5.89
  3   001999E3AEE8    13:00.2 Gigabit YES UEFI,PXE Enabled              1.5.89
  4   001999E3AEE9    13:00.3 Gigabit YES UEFI,PXE Enabled              1.5.89

./bootutil64e -ALL -UP=COMBO -FILE=../BootIMG.FLB should do the trickshot, then reboot, cold start to be sure. I cannot check if that works, because I have calculations running for days and can't have a downtime right now.
If that works and BootIMG.FLB from 26.6 contains firmware for I350, do the same for 30.3 or something in between...tldr; be sure you have the latest fw on all 6 ports.
And also possible that you need to find an older version between 20.4.1 and 26.4. These older versions will have also the DOS.exe, but I dunno exactly what was the last version with that.
If you download the .zip, you extract it twice. First time the .zip, second time extract the PREBOOT.exe just like zip file. Then in APPS/BootUtil you should see DOS-version if you have an old enough package. But the linux util should do the same.
 
Last edited:
mr44er said:
Can you post your output from proxmox (onboard and your card, preferable from all 6 ports)? https://www.intel.com/content/www/us/en/support/articles/000059457/ethernet-products.html
My 4 on the NIC are the same:
Code: 
ethtool -i enp13s0f0
driver: igb
version: 6.14.8-2-bpo12-pve
firmware-version: 1.52, 0x00000000, 1.3256.0
expansion-rom-version:
bus-info: 0000:0d:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

It seems that the preboot package 26.6 from 10/18/2021 already kicked out files for the I350, I dig further. Maybe even older package is needed.
Anyway in the readme from 26.6:


Edit:
Grab the preboot_26.6.tar.gz, shovel it into proxmox.
Code: 
tar -xvf preboot_26.6.tar.gz
cd APPS/BootUtil/Linux_x64
chmod +x bootutil64e
./bootutil64e
Connection to QV driver failed - please reinstall it!

Intel(R) Ethernet Flash Firmware Utility
BootUtil version 1.37.28.0
Copyright (C) 2003-2021 Intel Corporation

Type BootUtil -? for help

Port Network Address Location Series  WOL Flash Firmware                Version
==== =============== ======== ======= === ============================= =======
  1   001999E3AEE6    13:00.0 Gigabit YES UEFI,PXE Enabled              1.5.89
  2   001999E3AEE7    13:00.1 Gigabit YES UEFI,PXE Enabled              1.5.89
  3   001999E3AEE8    13:00.2 Gigabit YES UEFI,PXE Enabled              1.5.89
  4   001999E3AEE9    13:00.3 Gigabit YES UEFI,PXE Enabled              1.5.89

./bootutil64e -ALL -UP=COMBO -FILE=../BootIMG.FLB should do the trickshot, then reboot, cold start to be sure. I cannot check if that works, because I have calculations running for days and can't have a downtime right now.
If that works and BootIMG.FLB from 26.6 contains firmware for I350, do the same for 30.3 or something in between...tldr; be sure you have the latest fw on all 6 ports.
And also possible that you need to find an older version between 20.4.1 and 26.4. These older versions will have also the DOS.exe, but I dunno exactly what was the last version with that.
If you download the .zip, you extract it twice. First time the .zip, second time extract the PREBOOT.exe just like zip file. Then in APPS/BootUtil you should see DOS-version if you have an old enough package. But the linux util should do the same.
Click to expand...

Unfortunately, I can only get the two onboard ports. The ports on the card don't have a name, and it seems the command can't be run against an address, nor does there seem to be an equivalent command that can use the address. I'll grab some of the older packages and see what I come up with.

Meanwhile, my onboard looks similar to yours:

Code: 
root@PVE:/# ethtool -i enp4s0f0
driver: igb
version: 6.14.11-1-pve
firmware-version: 1.52.0
expansion-rom-version:
bus-info: 0000:04:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

root@PVE:/# ethtool -i enp4s0f1
driver: igb
version: 6.14.11-1-pve
firmware-version: 1.52.0
expansion-rom-version:
bus-info: 0000:04:00.1
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes

root@PVE:/# lspci | grep -i ethernet
04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
04:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
08:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
08:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
08:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
08:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)


root@PVE:/# lspci -v -s 04:00.0
04:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
        DeviceName:  Onboard Intel i350 Ethernet 1
        Subsystem: Super Micro Computer Inc X10DRW-i
        Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 26
        Memory at fb920000 (32-bit, non-prefetchable) [size=128K]
        I/O ports at d020 [size=32]
        Memory at fb944000 (32-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
        Capabilities: [a0] Express Endpoint, IntMsgNum 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 00-25-90-ff-ff-7c-2e-ea
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [1a0] Transaction Processing Hints
        Capabilities: [1c0] Latency Tolerance Reporting
        Capabilities: [1d0] Access Control Services
        Kernel driver in use: igb
        Kernel modules: igb



root@PVE:/# lspci -v -s 08:00.0
08:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
        Subsystem: Intel Corporation Ethernet Server Adapter I350-T4
        Flags: fast devsel, IRQ 65, IOMMU group 29
        Memory at 30000000 (32-bit, non-prefetchable) [size=1M]
        Memory at 30600000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at 30400000 [disabled] [size=512K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable- Count=10 Masked-
        Capabilities: [a0] Express Endpoint, IntMsgNum 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 98-b7-85-ff-ff-23-28-62
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [1a0] Transaction Processing Hints
        Capabilities: [1c0] Latency Tolerance Reporting
        Capabilities: [1d0] Access Control Services
        Kernel modules: igb

root@PVE:/# lspci -v -s 08:00.1
08:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
        Subsystem: Intel Corporation Ethernet Server Adapter I350-T4
        Flags: fast devsel, IRQ 65, IOMMU group 30
        Memory at 30100000 (32-bit, non-prefetchable) [size=1M]
        Memory at 30644000 (32-bit, non-prefetchable) [size=16K]
        Expansion ROM at 30480000 [disabled] [size=512K]
        Capabilities: [40] Power Management version 3
        Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
        Capabilities: [70] MSI-X: Enable- Count=10 Masked-
        Capabilities: [a0] Express Endpoint, IntMsgNum 0
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number 98-b7-85-ff-ff-23-28-62
        Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
        Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
        Capabilities: [1a0] Transaction Processing Hints
        Capabilities: [1d0] Access Control Services
        Kernel modules: igb
 
mike the newb said:
Unfortunately, I can only get the two onboard ports. The ports on the card don't have a name
Click to expand...
:confused:
You could temporarily deactivate the onboard ones, if that would help in some way..."to free up resources" if that should be the problem to grab them for the flashing procedure.

Code: 
root@xxx:~# lspci -v -s 0d:00.0
0d:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 17
    Memory at f5900000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d060 [size=32]
    Memory at f5f00000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5d00000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1c0] Latency Tolerance Reporting
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.1
0d:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 17
    Memory at f5a00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d040 [size=32]
    Memory at f5f44000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5d80000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.2
0d:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 17
    Memory at f5b00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d020 [size=32]
    Memory at f5f88000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5e00000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.3
0d:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 17
    Memory at f5c00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d000 [size=32]
    Memory at f5fcc000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5e80000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

And yes, I still think the old firmware here is not playing well with this newer mainboard and triggers the problems.
It's also possible that you'll have to perform several smaller intermediate steps between versions to flash. For example, first to v23, reboot, then v25, reboot, etc.
Switching directly to the latest version could also fail. I didn't read the readmes carefully, but there were references to this sometimes happening.
 
  • Like
Reactions: mike the newb
mr44er said:
:confused:
You could temporarily deactivate the onboard ones, if that would help in some way..."to free up resources" if that should be the problem to grab them for the flashing procedure.

Code: 
root@xxx:~# lspci -v -s 0d:00.0
0d:00.0 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 17
    Memory at f5900000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d060 [size=32]
    Memory at f5f00000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5d00000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1c0] Latency Tolerance Reporting
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.1
0d:00.1 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 17
    Memory at f5a00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d040 [size=32]
    Memory at f5f44000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5d80000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.2
0d:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 17
    Memory at f5b00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d020 [size=32]
    Memory at f5f88000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5e00000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

root@xxx:~# lspci -v -s 0d:00.3
0d:00.3 Ethernet controller: Intel Corporation I350 Gigabit Network Connection (rev 01)
    Subsystem: Fujitsu Technology Solutions I350 Gigabit Network Connection
    Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 17
    Memory at f5c00000 (32-bit, non-prefetchable) [size=1M]
    I/O ports at d000 [size=32]
    Memory at f5fcc000 (32-bit, non-prefetchable) [size=16K]
    Expansion ROM at f5e80000 [disabled] [size=512K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
    Capabilities: [70] MSI-X: Enable+ Count=10 Masked-
    Capabilities: [a0] Express Endpoint, MSI 00
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Device Serial Number 00-19-99-ff-ff-e3-ae-e6
    Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
    Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
    Capabilities: [1a0] Transaction Processing Hints
    Capabilities: [1d0] Access Control Services
    Kernel driver in use: igb
    Kernel modules: igb

And yes, I still think the old firmware here is not playing well with this newer mainboard and triggers the problems.
It's also possible that you'll have to perform several smaller intermediate steps between versions to flash. For example, first to v23, reboot, then v25, reboot, etc.
Switching directly to the latest version could also fail. I didn't read the readmes carefully, but there were references to this sometimes happening.
Click to expand...

I think you may be right about going incrementally. I'm pretty sure the reason the T4 card/ports don't have names is because of the memory reservation failing, so I'm literally stuck between the proverbial rock and hard place. I've got a new 4-port NIC that uses a Realtek chip coming today for testing purposes. I also forgot that I have a media/game machine I can put the T4 in to flash the firmware, then I can do the incremental thing with the onboard.
The media server is a PITA to pull out of it's location, so I may even resort to loading a "thin" windows build on one of my drives so I can boot to it and flash all the firmware. There is a windows installer in the package.
I'll definitely report back what I find.
 
mike the newb said:
I've got a new 4-port NIC that uses a Realtek chip coming today for testing purposes.
Click to expand...
In any case the Intel is better than the Realtek, but I think you know that. Doesn't help much if it won't work...I know. ;)

mike the newb said:
I'm pretty sure the reason the T4 card/ports don't have names is because of the memory reservation failing, so I'm literally stuck between the proverbial rock and hard place.
Click to expand...
Yeah, exactly.

mike the newb said:
There is a windows installer in the package.
Click to expand...
Rufus can build a win-to-go from .iso or something. But never tried that.
 
  • Like
Reactions: mike the newb
mr44er said:
In any case the Intel is better than the Realtek, but I think you know that. Doesn't help much if it won't work...I know. ;)


Yeah, exactly.


Rufus can build a win-to-go from .iso or something. But never tried that.
Click to expand...

I'll let you know. I'm doing the win-to-go right now. Nice thing is that this system has 16 hot swap drive bays so it's relatively painless. Think I'm going to do the same thing with Debian 13, though I don't think Rufus has a debian-to-go option. Guess I'll find out.
 
You must log in or register to reply here.
Top Bottom