{"id":239,"date":"2015-10-29T17:44:57","date_gmt":"2015-10-29T17:44:57","guid":{"rendered":"http:\/\/blog.ignoranthack.me\/?p=239"},"modified":"2015-10-29T17:44:57","modified_gmt":"2015-10-29T17:44:57","slug":"the-eeprom-you-have-reached-is-no-longer-in-service-freebsd-recovery-of-em4-devices","status":"publish","type":"post","link":"http:\/\/blog.ignoranthack.me\/?p=239","title":{"rendered":"The EEPROM you have reached is no longer in service, #FreeBSD recovery of em(4) devices"},"content":{"rendered":"<p>Ran into a very strange error with legacy em(4) devices on FreeBSD this week.\u00a0 Something I was doing while working on the EM_MULTIQUEUE kernel config option for em(4) seems to have blown up the PXE configuration in the EEPROM of one of my lem(4) devices.\u00a0 Else, cosmic rays did it:<\/p>\n<blockquote><p>em3: &lt;Intel(R) PRO\/1000 Legacy Network Connection 1.1.0&gt; port 0xe880-0xe8bf mem 0xfeb80000-0xfeb9ffff,0xfeb60000-0xfeb7ffff irq 19 at device 6.0 on pci5<br \/>\nem3: The EEPROM Checksum Is Not Valid<br \/>\ndevice_attach: em3 attach returned 5<\/p><\/blockquote>\n<p>It took me a while, but it seems when this happens, you can sometimes recover the device with <a href=\"https:\/\/downloadcenter.intel.com\/download\/19186\" target=\"_blank\">Intel&#8217;s Ethernet Connections Boot Utility.<\/a><\/p>\n<p>There is a DOS utility in this self-extracting CAB file called &#8220;bootutil&#8221; that can be used to reset your device to defaults.\u00a0 After prepping a DOS usb stick, I booted my host from it and ran the tool against all devices as I couldn&#8217;t quite tell which device was actually having the issues:<\/p>\n<blockquote><p>bootutil -all -defcfg<\/p><\/blockquote>\n<p>This cleared the error and now I get a successful attach.\u00a0 I literally have no idea what the problem was in the first place, but solved.<\/p>\n<p>Props to the <a href=\"http:\/\/ipxe.org\/howto\/romburning\/intel\" target=\"_blank\">IPXE<\/a> folks for having a great HOWTO on generically manipulating the firmware flash that gave me the clue on what to do.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Ran into a very strange error with legacy em(4) devices on FreeBSD this week.\u00a0 Something I was doing while working on the EM_MULTIQUEUE kernel config option for em(4) seems to have blown up the PXE configuration in the EEPROM of one of my lem(4) devices.\u00a0 Else, cosmic rays did it: em3: &lt;Intel(R) PRO\/1000 Legacy Network [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"_share_on_mastodon":"0"},"categories":[2],"tags":[],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/posts\/239"}],"collection":[{"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=239"}],"version-history":[{"count":1,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/posts\/239\/revisions"}],"predecessor-version":[{"id":240,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=\/wp\/v2\/posts\/239\/revisions\/240"}],"wp:attachment":[{"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=239"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=239"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.ignoranthack.me\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}