Date: Thu, 31 Jan 2019 20:36:22 +0100 From: Clayton Milos <clay@milos.co.za> To: Robert Blayzor <rblayzor.bulk@inoc.net>, Matthew Macy <mmacy@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: igb now em driver in FreeBSD 12.0 Message-ID: <kh4fvn9in4umdsdla8dud173.1548963382388@email.android.com> In-Reply-To: <CAPrugNqh4SQJYKOu7eWcWuFXH468B6zGHrYb3MC3_wY0t6kkcg@mail.gmail.com> References: <118b7a2c-f386-0d84-684f-7f8de99c85bf@inoc.net> <CAPrugNqh4SQJYKOu7eWcWuFXH468B6zGHrYb3MC3_wY0t6kkcg@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
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.bulk@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-unsubscribe@freebsd.org" >> >_______________________________________________ >freebsd-stable@freebsd.org mailing list >https://lists.freebsd.org/mailman/listinfo/freebsd-stable >To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kh4fvn9in4umdsdla8dud173.1548963382388>