I can confirm this. Had to change kernel conf to have em instead of igb and the device is detected as igb.
---- Matthew Macy wrote ---- >They show up as igb. The only POLA violation is that for users of modules >there is now no if_igb.ko so configuring an igb interface doesn't >automatically load the (em) module. > >On Thu, Jan 31, 2019 at 07:04 Robert Blayzor <rblayzor.b...@inoc.net> wrote: > >> Reading the release notes, the igb driver has been merged into the Intel >> em driver so that should be added to custom kernels. No problem. >> >> Question is, when the system reboots, are the NIC devices going to come >> up with "emX" now or will they remain "igbX" ? >> >> Kind of important to know on remote upgrading a server... >> >> >> -- >> inoc.net!rblayzor >> XMPP: rblayzor.AT.inoc.net >> PGP: https://inoc.net/~rblayzor/ >> >> _______________________________________________ >> freebsd-stable@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-stable >> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" >> >_______________________________________________ >freebsd-stable@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" _______________________________________________ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
