<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: network modules in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041812#M29434</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;in the lsmod command&lt;BR /&gt;e1000                 109113  0&lt;BR /&gt;bnx2                   84932  0&lt;BR /&gt;these both modules are displayed. Currently eth2 and 3 are up. But in the /etc/modprobe.conf its not mapped to the modules what it uses infact.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
    <pubDate>Mon, 23 Jul 2007 06:25:49 GMT</pubDate>
    <dc:creator>Adithyan</dc:creator>
    <dc:date>2007-07-23T06:25:49Z</dc:date>
    <item>
      <title>network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041810#M29432</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;In my servers I have 4 NIC. in the /etc/modprob.conf, it shows the modules used for eth0 and 1. Where shal i find the modules used for eth2 and eth3?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;Adithyan.</description>
      <pubDate>Mon, 23 Jul 2007 05:43:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041810#M29432</guid>
      <dc:creator>Adithyan</dc:creator>
      <dc:date>2007-07-23T05:43:19Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041811#M29433</link>
      <description>Are all 4 interfaces in use?&lt;BR /&gt;&lt;BR /&gt;If that's the case, I'm going to assume that eth2 and eth3 use the same drivers as eth0 and eth1.&lt;BR /&gt;&lt;BR /&gt;In which case, if you wish to differentiate between the different interfaces, you should use the HWADDR values in /etc/sysconfig/network-scripts/ifcfg-eth*.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jul 2007 06:16:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041811#M29433</guid>
      <dc:creator>Stuart Browne</dc:creator>
      <dc:date>2007-07-23T06:16:54Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041812#M29434</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;in the lsmod command&lt;BR /&gt;e1000                 109113  0&lt;BR /&gt;bnx2                   84932  0&lt;BR /&gt;these both modules are displayed. Currently eth2 and 3 are up. But in the /etc/modprobe.conf its not mapped to the modules what it uses infact.&lt;BR /&gt;&lt;BR /&gt;Regards</description>
      <pubDate>Mon, 23 Jul 2007 06:25:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041812#M29434</guid>
      <dc:creator>Adithyan</dc:creator>
      <dc:date>2007-07-23T06:25:49Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041813#M29435</link>
      <description>Try the file /etc/sysconfig/hwconf&lt;BR /&gt;&lt;BR /&gt;locate the occurrences of eth{0,1,2,3} and their driver.&lt;BR /&gt;</description>
      <pubDate>Mon, 23 Jul 2007 07:22:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041813#M29435</guid>
      <dc:creator>Alexander Chuzhoy</dc:creator>
      <dc:date>2007-07-23T07:22:30Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041814#M29436</link>
      <description>Thanks Alexander.&lt;BR /&gt;&lt;BR /&gt;Adithyan.</description>
      <pubDate>Mon, 23 Jul 2007 07:49:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041814#M29436</guid>
      <dc:creator>Adithyan</dc:creator>
      <dc:date>2007-07-23T07:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041815#M29437</link>
      <description>Hi Adithyan,&lt;BR /&gt;&lt;BR /&gt;U can even find driver used by an interface using "ethtool -i" command &lt;BR /&gt;&lt;BR /&gt;TEST&amp;gt; ethtool -i eth2&lt;BR /&gt;driver: e1000&lt;BR /&gt;version: 7.3.15a-NAPI&lt;BR /&gt;firmware-version: N/A&lt;BR /&gt;bus-info: 06:01.0&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regrads,&lt;BR /&gt;&lt;BR /&gt;SaC</description>
      <pubDate>Wed, 25 Jul 2007 06:30:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041815#M29437</guid>
      <dc:creator>Sac_3</dc:creator>
      <dc:date>2007-07-25T06:30:21Z</dc:date>
    </item>
    <item>
      <title>Re: network modules</title>
      <link>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041816#M29438</link>
      <description>I am not sure if this is still an issue with current kernels and driver kernel modules.&lt;BR /&gt;But for quite some time you needed to pass the kernel the boot param ether, where you would specify irq, base address and name.&lt;BR /&gt;For details please see man bootparam, and the Ethernet Devices section there.&lt;BR /&gt;There they also refer to this TLDP Ethernet HowTo for multiple devices issues:&lt;BR /&gt;&lt;A href="http://tldp.org/HOWTO/Ethernet-HOWTO-2.html#ss2.4" target="_blank"&gt;http://tldp.org/HOWTO/Ethernet-HOWTO-2.html#ss2.4&lt;/A&gt;</description>
      <pubDate>Wed, 25 Jul 2007 07:10:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/network-modules/m-p/4041816#M29438</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-07-25T07:10:28Z</dc:date>
    </item>
  </channel>
</rss>

