Re,
> So, I've just adjusted my build scripts and jenkins-job and hit the
> build button a few minutes ago to build a 5.9 stable image (yes it's not
> current, but I didn't see any changes in plus.html concerning em
> interfaces or pci stuff, but this will be the next step.
just as a short actual information on this topic. Booted with 5.9, but I
still see just the first 4 interfaces that belong to the first chip on
the card :
2:0:0: Intel I350 Fiber
2:0:1: Intel I350 Fiber
2:0:2: Intel I350 Fiber
2:0:3: Intel I350 Fiber
em0 at pci2 dev 0 function 0 "Intel I350 Fiber" rev 0x01: msi, address
00:90:0b:4b:54:0e
em1 at pci2 dev 0 function 1 "Intel I350 Fiber" rev 0x01: msi, address
00:90:0b:4b:54:0f
em2 at pci2 dev 0 function 2 "Intel I350 Fiber" rev 0x01: msi, address
00:90:0b:4b:54:10
em3 at pci2 dev 0 function 3 "Intel I350 Fiber" rev 0x01: msi, address
00:90:0b:4b:54:11
Unfortunately I'm just connected to a remote lab, so I neither can't
check the Bios settings or version concerning any PCI stuff nor perform
a "normal" installation.
Another question arised while looking at the supported media-types:
# ifconfig em1 media
em1: flags=18802<BROADCAST,SIMPLEX,MULTICAST,MPSAFE> mtu 1500
lladdr 00:90:0b:4b:54:0f
priority: 0
media: Ethernet autoselect (none)
status: no carrier
supported media:
media 1000baseSX mediaopt full-duplex
media 1000baseSX
media autoselect
#
Having a look at the specification and em(4) I thought, it would be
possible to connect e.g. 1000baseLX transceiver too.
Does anybody know, if it is just because there's no 1000baseLX plugged
in at the moment, or are there any limitations I should be aware of ?
So long,
Marco
