Don Buchholz <donald.buchh...@intel.com> wrote:
We can not (reliably) map the name "I219V" to a PCIe device. Use lspci(8) to ascertain the device id#, and then use modinfo(8) to see if that device ID is listed on one of the "alias" lines.
The fact that the driver loaded at all is a sign that the device is supported by the driver. If it were not, it would not have loaded and we would not see the checksum error complaint.
Finally, given dmesg output that you posted earlier, if the NVM checksum is bad, it really won't matter if your driver supports the hardware or not. The driver will not load if the hardware has been corrupted.
Actually, the driver did load because the device ID was recognized, but it will not activate any port that has a bad checksum. The NVM checksum issue needs to be addressed by your laptop maker.
-- Mark Rustad, Networking Division, Intel Corporation
signature.asc
Description: Message signed with OpenPGP using GPGMail
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev
_______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
