{"id":2290,"date":"2021-12-08T21:19:16","date_gmt":"2021-12-08T13:19:16","guid":{"rendered":"https:\/\/www.eumz.com\/?p=2290"},"modified":"2021-12-08T21:19:16","modified_gmt":"2021-12-08T13:19:16","slug":"redhat5%e3%80%81redhat6%e5%ae%89%e8%a3%85hp-dl380-dl580-g5-g6%e6%9c%8d%e5%8a%a1%e5%99%a8%e7%bd%91%e5%8d%a1%e9%a9%b1%e5%8a%a8%e6%ad%a5%e9%aa%a4","status":"publish","type":"post","link":"https:\/\/www.wxcn.com\/?p=2290","title":{"rendered":"redhat5\u3001redhat6\u5b89\u88c5HP DL380 DL580 G5 G6\u670d\u52a1\u5668\u7f51\u5361\u9a71\u52a8\u6b65\u9aa4"},"content":{"rendered":"\n

Installing the RPM Package<\/h1>\n\n\n\n
  1. This package requires a build environment. Please refer to the
    “Build Environment Setup” Section before proceding to the next step.<\/li>
  2. Install the source RPM package. rpm -ivh hp-e1000e-.src.rpm<\/li>
  3. Build the binary RPM for the e1000e driver. RHEL 5: rpmbuild -bb \/usr\/src\/redhat\/SPECS\/hp-e1000e.spec RHEL 6: rpmbuild -bb ~\/rpmbuild\/SPECS\/hp-e1000e.spec SLES: rpmbuild -bb \/usr\/src\/packages\/SPECS\/hp-e1000e.spec If you get an error during the build process, refer to the
    “Build Environment Setup” section. NOTE: One can build binary RPM for a specfic kernel flavor as follows: rpmbuild -bb SPECS\/hp-e1000e.spec –define “KVER ” NOTE: RHEL 5 x86 installations require the “–target” switch when
    building on Intel compatible machines. Please see the “Caveats”
    section below for more details. rpmbuild –target=i686 -bb \/usr\/src\/redhat\/SPECS\/hp-e1000e.spec<\/li>
  4. Check for the existence of a current version of the e1000e package as follows: RHEL rpm -q kmod-hp-e1000e- SLES rpm -q hp-e1000e-kmp- If an old version of the package exists, the RPM package should be
    removed. Remove the corresponding tools package before removing
    driver package. RHEL rpm -e kmod-hp-e1000e- SLES rpm -e hp-e1000e-kmp- Verify if the old hp-e1000e package has been removed as follows: RHEL rpm -q kmod-hp-e1000e- SLES rpm -q hp-e1000e-kmp-<\/li>
  5. Install the new binary RPM package. RHEL 5 rpm -ivh \\ \/usr\/src\/redhat\/RPMS\/\/kmod-hp-e1000e–..rpm RHEL 6 rpm -ivh \\ ~\/rpmbuild\/RPMS\/\/kmod-hp-e1000e–..rpm The modules are installed in the following directory:
    \/lib\/modules\/\/extra\/hp-e1000e Note: The “–nodeps” switch is required when installing on RHEL 5.5. See
    “Caveats” section below for more details. rpm -ivh \\ \/usr\/src\/redhat\/RPMS\/\/kmod-hp-e1000e–..rpm –nodeps SLES rpm -ivh RPMS\/\/hp-e1000e-kmp–..rpm The modules are installed in the following directory:
    \/lib\/modules\/\/updates\/hp-e1000e<\/li>
  6. Configure your network setting and address. You may need to refer to your
    Linux vendor documentation. Helpful network configuration tools such as
    “yast2” in SLES or linuxconf\/redhat-config-network\/netconfig in Red Hat
    exist for easy configuration.<\/li><\/ol>\n\n\n\n

    For SLES, user may have to specify the module as e1000e while configuring
    the network. The module can be specified in Hardware Details of Advanced
    configuration<\/p>\n\n\n\n

    1. Ensure that the \/etc\/modules.conf file is configured similar to the example
      listed below. The example below is presented as if more than one adapter is
      present. If so, one eth# instance should exist for each ethernet port. Refer to
      the modules.conf man page for more information. alias eth0 e1000e
      alias eth1 e1000e<\/li><\/ol>\n\n\n\n

      For SLES, the configuration file is \/etc\/modprobe.conf or \/etc\/modprobe.conf.local<\/p>\n\n\n\n

      1. You can now reboot your server or restart the network services. Upon reboot
        the network should start with the e1000e driver loaded<\/li><\/ol>\n\n\n\n

        To verify that the e1000e driver is loaded use the following command.<\/p>\n\n\n\n

        # lsmod<\/code><\/pre>\n\n\n\n
        You should find e1000e listed. You can also verify if the correct e1000e driver is
        loaded through any of the following methods. Note that version of the driver loaded
        should be same as that of the package version.<\/p>\n\n\n\n
        A. Look for driver load messages in the system log.<\/p>\n\n\n\n
        #dmesg | grep Intel<\/code><\/pre>\n\n\n\n
        You should see messages of the following type,<\/p>\n\n\n\n
        Intel(R) PRO\/1000 Network Driver - version x.x.x<\/code><\/pre>\n\n\n\n
        B. Check the \/var\/log\/messages file for a similar message as indicated in method A.<\/p>\n\n\n\n
        Note: To load the driver from command line use ‘modprobe’ instead of ‘insmod’.
        Refer to the man pages for lsmod, ifconfig, rmmod, insmod, modprobe, modules.conf
        and modprobe.conf for more detailed information.<\/p>\n\n\n\n
        Uninstalling the RPM<\/h1>\n\n\n\n
        The following command will uninstall the RPM.<\/p>\n\n\n\n
        Red Hat\n# rpm -e kmod-hp-e1000e-<kernel flavor>\n\nSLES\n# rpm -e hp-e1000e-kmp-<kernel flavor><\/code><\/pre>\n\n\n\n
        Limitations<\/h1>\n\n\n\n
        Some Linux distributions may not add the default route back to a specified network
        device when a network stop\/start command is used. Use the route command to add the
        default router back to the network device.<\/p>\n\n\n\n
        Some Linux distributions may not add the default assigned IP address back to a
        specified network device when using the following:<\/p>\n\n\n\n
        ifconfig eth(x) down\nrmmod <module name>\ninsmod <module name> <optional parameter changes>\nifconfig eth(x) up<\/code><\/pre>\n\n\n\n
        Another step to reassign the IP address back to the device may be required:<\/p>\n\n\n\n
        ifconfig eth(x) <ip address><\/code><\/pre>\n\n\n\n
        Some Linux distributions may add multiple IP addresses with the same system name in
        the \/etc\/hosts file when configuring multiple network devices.<\/p>\n","protected":false},"excerpt":{"rendered":"
        Installing the RPM Package This package requires a buil […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3,4],"tags":[237,542,592],"class_list":["post-2290","post","type-post","status-publish","format-standard","hentry","category-operating-system","category-pcserver","tag-redhat","tag-542","tag-592"],"_links":{"self":[{"href":"https:\/\/www.wxcn.com\/index.php?rest_route=\/wp\/v2\/posts\/2290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wxcn.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wxcn.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wxcn.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wxcn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2290"}],"version-history":[{"count":0,"href":"https:\/\/www.wxcn.com\/index.php?rest_route=\/wp\/v2\/posts\/2290\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wxcn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wxcn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wxcn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}