In two separate letters, ASUS customer service acknowledged that, according to my description, the NVM problem might be technical and not related to Linux, and they replied that they do not have tools for checking or restoring the contents of the NVM, but if i find any, they will be glad if i let them know.
Luckily for me, the online store where i bought the laptop accepted to exchange it for a new one. I am anxious to see how the new one will behave... - Alexey. On 20 Jul 2016, at 21:21, Rustad, Mark D <mark.d.rus...@intel.com> wrote: > Alexey Muranov <alexey.mura...@gmail.com> wrote: > >> I wrote to Asus (my laptop maker), and they responded that they can only >> help with setting up the original hardware and software, and they cannot >> help if i have installed Linux, because the laptop was sold with Windows. I >> wrote to them again explaining that it looks like there is a hardware >> problem. I am waiting for an answer, but taking into account that Ethernet >> works under Windows 7, i imagine they can keep refusing to take care of my >> problem. > > Possibly, unless you can get the issue escalated to a higher level of support > somehow. It is not a surprise that the "front line" can only deal with > Windows. > > If they can provide a tool to modify the MAC address in the NVM, you may be > able to use such a tool to correct the checksum by setting a different MAC > address, and then setting the original MAC address back. That would only work > if the tool they provide properly calculates the checksum, but there is at > least a possibility that it would. > >> Could you recommend me by any chance some tests to run under Windows and >> some Intel Ethernet Connection documentation to demonstrate to Asus that i >> have a hardware problem? > > You probably won't find anything wrong in that way. The Windows driver > doesn't check the checksum, so if it works properly under Windows, it is very > likely that the only thing wrong is the checksum itself. I doubt very much > that there is a true hardware problem - just an incorrect checksum. > > Correcting the NVM checksum is the best solution, but modifying your system's > NVM is something best done by your vendor or by tools and directions provided > by your vendor. The potential for bricking the laptop is the reason to be > very careful with NVM issues. > > If you are able and willing, something that can be tried is to modify the > driver to not error out on a bad checksum. If that works, it would tend to > confirm that the only problem is the checksum itself. There are all kinds of > issues with doing that so I am not strongly advocating doing that but only > offering it as something to try if you understand what you are getting into > when modifying drivers. > > -- > Mark Rustad, Networking Division, Intel Corporation ------------------------------------------------------------------------------ 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
