I have a board with multiple external PCIe Ethernet I350 chips.
In my lspci I have: 03.00.0 (4-port I350) 03.00.1 03.00.2 03.00.3 04.00.0 (4-port I350) 04.00.1 04.00.2 04.00.3 05.00.0 (2-port I350) 05.00.1
I builtin iPXE image to coreboot and I have all of these devices in Seabios bootmenu. But the problem is that I can only boot from ports of the first appeared chip. In the example above it will be 03.00.x boot devices. If I'll physically unplug 03.00.x chip, I'll be able to boot from 04.00.x boot devices. And if I'll unplug 03.00.x and 04.00.x chip, I'll be able to boot from 05.00.x boot devices.
Does someone had the same problem and is there any idea of how to solve it?
Coreboot+SeaBIOS log is in attachment (it has some additional printk's)
On Wed, Dec 28, 2016 at 05:18:32PM +0300, Аладышев Константин wrote:
I have a board with multiple external PCIe Ethernet I350 chips.
In my lspci I have: 03.00.0 (4-port I350) 03.00.1 03.00.2 03.00.3 04.00.0 (4-port I350) 04.00.1 04.00.2 04.00.3 05.00.0 (2-port I350) 05.00.1
I builtin iPXE image to coreboot and I have all of these devices in Seabios bootmenu. But the problem is that I can only boot from ports of the first appeared chip. In the example above it will be 03.00.x boot devices. If I'll physically unplug 03.00.x chip, I'll be able to boot from 04.00.x boot devices. And if I'll unplug 03.00.x and 04.00.x chip, I'll be able to boot from 05.00.x boot devices.
Does someone had the same problem and is there any idea of how to solve it?
That's odd. I'd ask on the iPXE mailing list - it would seem the roms on the different cards are trying to coordinate and something isn't working. There isn't much in the SeaBIOS debug log to help diagnose the root cause.
-Kevin